User Plane Function Selection For Isolated Network Slice

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. A session request for a wireless device may comprise a network slice isolation information parameter. A user plane function may be selected, based on the network slice isolation information parameter, to provide the requested session for the wireless device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/596,237, titled “UPF Selection For Isolated Network Slice” and filedDec. 8, 2017, the disclosure of which is hereby incorporated byreference in its entirety.

BACKGROUND

Some wireless services may use network slices that differ from othernetwork slices. One or more network devices that provide some servicesfor a wireless device may not accommodate certain network slices thatmay be required for other services. As a result, difficulties may arisefor a wireless device to obtain desired services.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for providing anisolated network slice for a wireless device. A wireless device mayrequest services that may require an isolated network slice. Thewireless device may send a packet data unit (PDU) session that maycomprise a parameter associated with an isolated network slice. Asession management function may determine that user plane functionshould be selected to accommodate the requested services for thewireless device. For example, some user planes may not be configured foran isolated network slice that may be required for the requestedservices. A user plane function may be selected to provide the requestedservices. The user plane function may be selected based on the parameterassociated with the isolated network slice. A PDU session may beestablished for the wireless device using the selected user planefunction to provide the requested services for the wireless device.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example 5G system architecture.

FIG. 2 shows an example 5G system architecture.

FIG. 3 shows an example of a wireless device and a network node.

FIGS. 4A and 4B show example elements of computing devices that may beused to implement any of the various devices described herein.

FIG. 5 shows examples of registration management state models for awireless device and an access and mobility management function (AMF).

FIG. 6 shows examples of connection management state models for awireless device and an AMF.

FIG. 7 shows an example for classifying and marking traffic.

FIGS. 8A-B shows examples of registration procedures.

FIG. 9 shows an example of control plane interfaces for network slicing.

FIG. 10 shows an example of wireless devices assigned to core part of anetwork slice instance (NSI).

FIG. 11 shows an example of network slice architecture with twogroups-common control plane (CP) network functions (NFs) and dedicatedCP NFs.

FIG. 12 shows an example of multiple network slices per wireless device.

FIG. 13A and FIG. 13B shows example methods for service requests.

FIG. 14 shows an example method for establishing an isolated networkslice.

FIG. 15 shows an example method for establishing an isolated networkslice.

FIG. 16 shows an example of a partially isolated network slice with ashared (radio) access network ((R)AN).

FIG. 17 shows an example of a partially isolated network slice with ashared (R)AN and a shared session management function (SMF).

FIG. 18 shows an example of a first user plane instance controlled bymultiple SMFs.

FIG. 19 shows an example of two fully isolated network slices.

FIG. 20 shows an example of a partially isolated network slice with ashared (R)AN.

FIG. 21 shows an example of a partial isolation of two network sliceswith a shared (R)AN and a shared access and mobility management function(AMF).

FIG. 22 shows an example method for providing an isolated network slice.

FIG. 23 shows an example of a user plane selection based on an isolationconstraint.

FIG. 24 shows an example method that may be performed by an SMF toprovide an isolated network slice.

FIG. 25 shows an example method that may be performed by a networkrepository function (NRF) to provide an isolated network slice.

FIG. 26 shows an example method that may be performed by a wirelessdevice and/or a base station for an isolated network slice.

DETAILED DESCRIPTION

The accompanying drawings, which form a part hereof, show examples ofthe disclosure. It is to be understood that the examples shown in thedrawings and/or discussed herein are non-exclusive and that there areother examples of how the disclosure may be practiced.

Examples of enhanced features and functionalities in networks, such as5G networks, or other systems are provided. The technology disclosedherein may be employed in the technical field of networks, such as 5Gsystems, and Ethernet type PDU sessions for communication systems. Moreparticularly, the technology disclosed herein may relate to for networkslicing in communication systems such as 5GC, 5G, or other systems. Thecommunication systems may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices.

The following acronyms are used throughout the present disclosure,provided below for convenience although other acronyms may be introducedin the detailed description.

-   5G 5th generation mobile networks-   5GC 5G Core Network-   5GS 5G System-   5G-AN 5G Access Network-   5QI 5G QoS Indicator-   AF Application Function-   AMF Access and Mobility Management Function-   AN Access Network-   CDR Charging Data Record-   CCNF Common Control Network Functions-   CIoT Cellular IoT-   CN Core Network-   CP Control Plane-   DDN Downlink Data Notification-   DL Downlink-   DN Data Network-   DNN Data Network Name-   eNB Evolved Node B-   gNB Next Generation Node B or NR Node B-   F-TEID Fully Qualified TEID-   GPSI Generic Public Subscription Identifier-   GTP GPRS Tunneling Protocol-   IMSI International Mobile Subscriber Identity-   LADN Local Area Data Network-   LI Lawful Intercept-   MEI Mobile Equipment Identifier-   MICO Mobile Initiated Connection Only-   MME Mobility Management Entity-   MO Mobile Originated-   MSISDN Mobile Subscriber ISDN-   MT Mobile Terminating-   N3IWF Non-3GPP InterWorking Function-   NAI Network Access Identifier-   NAS Non-Access Stratum-   NB-IoT Narrow Band IoT-   NEF Network Exposure Function-   NF Network Function-   NGAP Next Generation Application Protocol-   NR New Radio-   NRF Network Repository Function-   NSSAI Network Slice Selection Assistance Information-   PCF Policy Control Function-   PDU Packet Data Unit-   PEI Permanent Equipment Identifier-   PLMN Public Land Mobile Network-   (R)AN (Radio) Access Network-   QFI QoS Flow Identity-   RM Registration Management-   S1-AP S1 Application Protocol-   SBA Service Based Architecture-   SEA Security Anchor Function-   SCM Security Context Management-   SMF Session Management Function-   SMSF SMS Function-   S-NSSAI Single Network Slice Selection Assistance information-   SUPI Subscriber Permanent Identifier-   TEID Tunnel Endpoint Identifier-   UDM Unified Data Management-   UE User Equipment-   UL Uplink-   UL CL Uplink Classifier-   UPF User Plane Function-   VPLMN Visited Public Land Mobile Network

FIG. 1 and FIG. 2 show examples 5G system architecture. A 5G accessnetwork may comprise an access network connecting to a 5GC. An accessnetwork may comprise an AN 105 (e.g., NG-RAN such as in FIG. 1, or anyaccess node as in FIG. 2) and/or non-3GPP AN 165 which may be anuntrusted AN. An example 5GC may connect to one or more 5G accessnetworks (e.g., a 5G AN) and/or NG-RANs. The 5GC may comprise functionalelements or network functions as in example FIG. 1 and example FIG. 2,where interfaces may be employed for communication among the functionalelements and/or network elements. A network function may be a processingfunction in a network that has a functional behavior and interfaces. Anetwork function may be implemented as a network element on a dedicatedhardware, a base station, and/or as a software instance running on adedicated hardware, shared hardware, and/or as a virtualized functioninstantiated on an appropriate platform.

The access and mobility management function AMF 155 may comprise one ormore of the following functionalities: termination of (R)AN CP interface(N2), termination of NAS (N1), NAS ciphering and integrity protection,registration management, connection management, reachability management,mobility management, lawful intercept (for AMF events and interface toLI system), transport for session management, SM messages between awireless device 100 and an SMF 160, transparent proxy for routing SMmessages, access authentication, access authorization, transport forshort message service (SMS) messages between wireless device 100 and anSMS function (SMSF), security anchor function (SEA) interaction with theAUSF 150 and the wireless device 100, receiving an intermediate keyestablished as a result of the wireless device 100 authenticationprocess, security context management (SCM), and/or receiving a key fromthe SEA to derive access network specific keys. A variety of thesefunctionalities may be supported in a single instance of an AMF 155and/or in multiple instances of AMF 155 as appropriate.

The AMF 155 may support non-3GPP access networks via an N2 interfacewith N3IWF 170, NAS signaling with a wireless device 100 over N3IWF 170,authentication of wireless devices connected over N3IWF 170, managementof mobility, authentication, and separate security context state(s) of awireless device 100 connected via non-3GPP access 165 or connected via3GPP access 105 and non-3GPP accesses 165 simultaneously, support of acoordinated RM context valid over 3GPP access 105 and non-3GPP access165, and/or support of context management (CM) management contexts forthe wireless device 100 for connectivity over non-3GPP access. Somefunctionalities described above may be supported in an instance of anetwork slice. An AMF 155 region may comprise of one or multiple AMF 155sets. AMF 155 set may comprise of some AMFs 155 that serve a given areaand/or network slice(s). Multiple AMF 155 sets may be per AMF 155 regionand/or network slice(s). Application identifiers may be mapped to one ormore specific application traffic detection rules. A configured NSSAImay be a NSSAI that has been provisioned in a wireless device 100. DN115 access identifier (DNAI), for a DNN, may be an identifier of a userplane access to a DN 115. Initial registration may be related to awireless device 100 registration in a RM-DEREGISTERED state. N2APwireless device 100 association may be a logical per wireless device 100association between a 5G AN node and an AMF 155. Wireless device 100 maycomprise a N2AP wireless device-TNLA-binding, which may be a bindingbetween a N2AP wireless device 100 association and a specific transportnetwork layer (TNL) association for a given wireless device 100.

The session management function (SMF) 160 may comprise one or more ofthe following functionalities: session management (e.g., sessionestablishment, modify and release, comprising tunnel maintain betweenUPF 110 and AN 105 node), wireless device IP address allocation &management (comprising optional authorization), selection and control ofuser plane function(s), configuration of traffic steering at UPF 110 toroute traffic to its proper destination, termination of interfacestowards policy control functions, control part of policy enforcement andQoS, lawful intercept (for SM events and interface to LI system),termination of SM parts of NAS messages, downlink data notification,initiation of AN specific SM information, sent via AMF 155 over N2 to(R)AN 105, determination of SSC mode of a session, roamingfunctionality, handling local enforcement to apply QoS SLAs (VPLMN),charging data collection and charging interface (VPLMN), lawfulintercept (in VPLMN for SM events and interface to LI system), and/orsupport for interaction with external DN 115 for transport of signalingfor PDU session authorization/authentication by external DN 115. One ormore of these functionalities may be supported in a single instance of aSMF 160. One or more of the functionalities described above may besupported in an instance of a network slice.

The user plane function (UPF) 110 may comprise one or more of thefollowing functionalities: anchor point for Intra-/Inter-RAT mobility(if applicable), external PDU session point of interconnect to DN 115,packet routing & forwarding, packet inspection and user plane part ofpolicy rule enforcement, lawful intercept (UP collection), traffic usagereporting, uplink classifier to support routing traffic flows to a datanetwork, branching point to support multi-homed PDU session(s), QoShandling for user plane, uplink traffic verification (SDF to QoS flowmapping), transport level packet marking in the uplink and downlink,downlink packet buffering, and/or downlink data notification triggering.One or more of these functionalities may be supported in a singleinstance of a UPF 110. One or more of functionalities described abovemay be supported in an instance of a network slice. User planefunction(s) (UPF(s) 110) may handle the user plane path of PDU sessions.A UPF 110 that provides the interface to a data network supports thefunctionality of a PDU session anchor.

IP address management may comprise allocation and release of thewireless device IP address as well as renewal of the allocated IPaddress. The wireless device 100 sets the requested PDU type during thePDU session establishment procedure based on its IP stack capabilitiesand configuration. The SMF 160 may select PDU type of a PDU session asfollows: if the SMF 160 receives a request with PDU type set to IP, theSMF 160 may select either PDU type IPv4 or IPv6 based on DNNconfiguration and/or operator policies. The SMF 160 may also provide acause value to the wireless device 100 to indicate whether the other IPversion (e.g. IPv6 if IPv4 is selected and vice versa) may be supportedon the DNN. If the other IP versions are supported, wireless device 100may request another PDU session to the same DNN for the other IPversion. If the SMF 160 receives a request for PDU type IPv4 or IPv6 andthe requested IP version may be supported by the DNN, the SMF 160selects the requested PDU type. The 5GC elements and wireless device 100support the following mechanisms: during PDU session establishmentprocedure, the SMF 160 may send the IP address to the wireless device100 via SM NAS signaling. The IPv4 address allocation and/or IPv4parameter configuration via DHCPv4 may also be used if the PDU sessionmay be established. IPv6 prefix allocation may be supported via IPv6stateless auto configuration, if IPv6 may be supported. IPv6 parameterconfiguration via stateless DHCPv6 may also be supported. The 5GC maysupport the allocation of a static IPv4 address and/or a static IPv6prefix based on subscription information in the UDM 140 or based on theconfiguration on a per-subscriber, per-DNN basis.

The policy control function PCF 135 may support unified policy frameworkto govern network behavior, provide policy rules to control planefunction(s) to enforce them, and/or implement a front end to accesssubscription information relevant for policy decisions in a user datarepository (UDR). The unified data management UDM 140 may comprise anapplication front end (FE) that comprises the UDM-FE that may be incharge of processing credentials, location management, and/orsubscription management. The PCF 135 may be in charge of policy controland the user data repository (UDR) that stores data required forfunctionalities provided by UDM-FE, plus policy profiles required by thePCF 135. The data stored in the UDR may comprise at least usersubscription data, comprising at least subscription identifiers,security credentials, access and mobility related subscription data,session related subscription data, and/or policy data.

The network exposure function NEF 125 may provide a means to securelyexpose the services and capabilities provided by the 3GPP networkfunctions, translate between information exchanged with the AF 145 andinformation exchanged with the internal network functions, and/orreceive information from other network functions.

The NF repository function NRF 130 may support a service discoveryfunction that receives NF discovery requests from a NF instance,provides the information of the discovered NF instances to the NFinstance, and/or maintains the information of available NF instances andtheir supported services.

The network slice selection function (NSSF) 120 may support selectingthe set of network slice instances serving the wireless device 100,determining the provided NSSAI, determining the AMF 155 set to beemployed to serve the wireless device 100, and/or, based onconfiguration, determining a list of candidate AMF(s) 155, possibly byquerying the NRF 130.

The functionality of non-3GPP interworking function N3IWF 170 fornon-3GPP access 165 may comprise at least one or more of the following:supporting of IPsec tunnel establishment with the wireless device,terminating the IKEv2/IPsec protocols with the wireless device 100 overNWu, relaying over N2 the information needed to authenticate thewireless device 100 and authorize its access to the 5GC, terminating ofN2 and N3 interfaces to 5GC for control-plane and user-planerespectively, relaying uplink and downlink control-plane NAS (N1)signaling between the wireless device 100 and AMF 155, handling of N2signaling from SMF 160 (which may be relayed by AMF 155) related to PDUsessions and QoS, establishing of IPsec security association (IPsec SA)to support PDU session traffic, relaying uplink and downlink user-planepackets between the wireless device 100 and UPF 110, enforcing QoScorresponding to N3 packet marking, considering QoS requirementsassociated to such marking received over N2, N3 user-plane packetmarking in the uplink, local mobility anchor within untrusted non-3GPPaccess networks 165 using MOBIKE, and/or supporting AMF 155 selection.

The application function AF 145 may interact with the 3GPP core networkto provide a variety of services. Based on operator deployment, AF 145may be trusted by the operator to interact directly with relevantnetwork functions. Application functions not provided by the operator toaccess directly the network functions may use the external exposureframework (via the NEF 125) to interact with relevant network functions.

The control plane interface between the (R)AN 105 and the 5GC maysupport connection of multiple different kinds of ANs, such as 3GPP(R)AN 105 and/or N3IWF 170, to the 5GC via a unique control planeprotocol. A single N2 AP protocol may be employed for both the 3GPPaccess 105 and non-3GPP access 165 and/or for decoupling between AMF 155and other functions such as SMF 160 that may need to control theservices supported by AN(s) (e.g. control of the UP resources in the AN105 for a PDU session). The 5GC may be able to provide policyinformation from the PCF 135 to the wireless device 100. Such policyinformation may comprise the following: access network discovery &selection policy, wireless device route selection policy (URSP) thatgroups to or more of SSC mode selection policy (SSCMSP), network sliceselection policy (NSSP), DNN selection policy, and/or non-seamlessoffload policy. The 5GC may support the connectivity of a wirelessdevice 100 via non-3GPP access networks 165. As shown in example FIG. 5,the registration management, RM may be employed to register orde-register a wireless device 100 with the network, and establish theuser context in the network. Connection management may be employed toestablish and release the signaling connection between the wirelessdevice 100 and the AMF 155.

A wireless device 100 may need to register with the network to receiveservices that require registration. The wireless device 100 may updateits registration with the network, e.g., periodically, after thewireless device is registered, to remain reachable (e.g. periodicregistration update), on mobility (e.g. mobility registration update),and/or to update its capabilities or re-negotiate protocol parameters.An initial registration procedure, such as in the examples shown in FIG.8A and FIG. 8B, may involve execution of network access controlfunctions (e.g. user authentication and access authorization based onsubscription profiles in UDM 140). As result of the registrationprocedure, the identity of the serving AMF 155 may be registered in UDM140. The registration management (RM) procedures may be applicable overboth 3GPP access 105 and non-3GPP access 165.

FIG. 3 shows hardware elements of a network node 320 (e.g., a basestation) and a wireless device 310. A communication network may includeat least one network node 320 and at least one wireless device 310. Thenetwork node 320 may include one or more communication interface 322,one or more processors 324, and one or more sets of program codeinstructions 328 stored in non-transitory memory 326 and executable bythe one or more processors 324. The wireless device 310 may include oneor more communication interface 312, one or more processors 314, and oneor more sets of program code instructions 318 stored in non-transitorymemory 316 and executable by the one or more processors 314. Acommunication interface 322 in the network node 320 may be configured toengage in communication with a communication interface 312 in thewireless device 310, such as via a communication path that includes atleast one wireless link. The wireless link may be a bi-directional link.The communication interface 312 in the wireless device 310 may also beconfigured to engage in communication with the communication interface322 in the network node 320. The network node 320 and the wirelessdevice 310 may be configured to send and receive data over the wirelesslink using multiple frequency carriers. Network nodes, base stations,wireless devices, and other communication devices may include structureand operations of transceiver(s). A transceiver is a device thatincludes both a transmitter and receiver. Transceivers may be employedin devices such as wireless devices, base stations, relay nodes, and/orthe like. Examples for radio technology implemented in the communicationinterfaces 312, 322 and the wireless link are shown in FIG. 3, FIGS. 4A,and 4B, and associated text. The communication network may comprise anynumber and/or type of devices, such as, for example, computing devices,wireless devices, mobile devices, handsets, tablets, laptops, internetof things (IoT) devices, hotspots, cellular repeaters, computingdevices, and/or, more generally, user equipment (e.g., UE). Although oneor more of the above types of devices may be referenced herein (e.g.,UE, wireless device, computing device, etc.), it should be understoodthat any device herein may comprise any one or more of the above typesof devices or similar devices. The communication network, and any othernetwork referenced herein, may comprise an LTE network, a 5G network, orany other network for wireless communications. Apparatuses, systems,and/or methods described herein may generally be described asimplemented on one or more devices (e.g., wireless device, base station,eNB, gNB, computing device, etc.), in one or more networks, but it willbe understood that one or more features and steps may be implemented onany device and/or in any network. As used throughout, the term “basestation” may comprise one or more of: a base station, a node, a Node B,a gNB, an eNB, an ng-eNB, a relay node (e.g., an integrated access andbackhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB,etc.), an access point (e.g., a WiFi access point), a computing device,a device capable of wirelessly communicating, and/or any other devicecapable of sending and/or receiving signals. As used throughout, theterm “wireless device” may comprise one or more of: a UE, a handset, amobile device, a computing device, a node, a device capable ofwirelessly communicating, and/or any other device capable of sendingand/or receiving signals. Any reference to one or more of theseterms/devices also considers use of any other term/device mentionedabove.

The communications network may comprise Radio Access Network (RAN)architecture. The RAN architecture may comprise one or more RAN nodesthat may be a next generation Node B (gNB) (e.g., 320) providing NewRadio (NR) user plane and control plane protocol terminations towards afirst wireless device (e.g. 310). A RAN node may be a next generationevolved Node B (ng-eNB), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device. The first wireless device may communicate with agNB over a Uu interface. The second wireless device may communicate witha ng-eNB over a Uu interface. The network node 320 may comprise one ormore of a gNB, ng-eNB, and/or the like.

A gNB or an ng-eNB may host functions such as: radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of wirelessdevices in RRC_INACTIVE state, distribution function for Non-AccessStratum (NAS) messages, RAN sharing, and dual connectivity or tightinterworking between NR and E-UTRA.

One or more gNBs and/or one or more ng-eNBs may be interconnected witheach other by means of Xn interface. A gNB or an ng-eNB may be connectedby means of NG interfaces to 5G Core Network (5GC). 5GC may comprise oneor more AMF/User Plane Function (UPF) functions. A gNB or an ng-eNB maybe connected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g., non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (e.g., NG-C) interface. The NG-C interface may provide functionssuch as NG interface management, UE context management, UE mobilitymanagement, transport of NAS messages, paging, PDU session management,configuration transfer or warning message transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (if applicable), external PDU sessionpoint of interconnect to data network, packet routing and forwarding,packet inspection and user plane part of policy rule enforcement,traffic usage reporting, uplink classifier to support routing trafficflows to a data network, branching point to support multi-homed PDUsession, QoS handling for user plane, for example, packet filtering,gating, Uplink (UL)/Downlink (DL) rate enforcement, uplink trafficverification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling for mobility between 3rd GenerationPartnership Project (3GPP) access networks, idle mode UE reachability(e.g., control and execution of paging retransmission), registrationarea management, support of intra-system and inter-system mobility,access authentication, access authorization including check of roamingrights, mobility management control (subscription and policies), supportof network slicing and/or Session Management Function (SMF) selection

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

FIG. 4A shows general hardware elements that may be used to implementany of the various computing devices discussed herein, including anybase station, wireless device, or computing device. The computing device400 (e.g., wireless device) may include one or more processors 418,which may execute instructions stored memory, such as non-removablememory 430, removable memory 432 (such as a Universal Serial Bus (USB)drive, compact disk (CD) or digital versatile disk (DVD), or floppy diskdrive), or any other desired storage medium. Instructions may also bestored in an attached (or internal) hard drive. The computing device 400may also include a security processor (not shown), which may executeinstructions of a one or more computer programs to monitor the processesexecuting on the processor 418 and any process that requests access toany hardware and/or software components of the computing device 400(e.g., the non-removable memory 430, the removable memory 432, the harddrive, a device controller (e.g., a keypad 426, a display and/ortouchpad 428, a speaker and/or microphone 424, and/or one or moreperipherals 438), a transceiver 420, a network interface, a GPS 436(e.g., a GPS chipset), a Bluetooth interface, a WiFi interface, etc.).The computing device 400 may include one or more output devices, such asthe display and/or touchpad 428 (e.g., a screen, a display device, amonitor, a television, etc.), and may include one or more output devicecontrollers, such as a video processor. There may also be one or moreuser input devices, such as a remote control, keyboard, mouse, touchscreen, microphone, etc., that may be configured, for example, as one ormore of the peripherals 438. The computing device 400 may also includeone or more network interfaces, such as a network interface, the may bea wired interface, a wireless interface such as the transceiver 420, ora combination of the two. The network interface may provide an interfacefor the computing device 400 to communicate (e.g., via communications416) with a network (e.g., a RAN, or any other network). The networkinterface may include a modem (e.g., a cable modem), and the externalnetwork may include communication links, an external network, an in-homenetwork, a provider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 400 may include alocation-detecting device, such as a global positioning system (GPS)chipset or microprocessor 436, which may be configured to receive andprocess global positioning signals and determine, with possibleassistance from an external server and antenna (e.g., antenna 422), ageographic position of the computing device 400.

FIG. 4B shows general hardware elements that may be used to implementany of the various computing devices discussed herein, including, e.g.,the network node 320, the wireless device 310, or any other networknode, base station, wireless device, or computing device describedherein. The computing device 4000 may include one or more processors4001, which may execute instructions stored in the random access memory(RAM) 4003, the removable media 4004 (such as a Universal Serial Bus(USB) drive, compact disk (CD) or digital versatile disk (DVD), orfloppy disk drive), or any other desired storage medium. Instructionsmay also be stored in an attached (or internal) hard drive 4005. Thecomputing device 4000 may also include a security processor (not shown),which may execute instructions of one or more computer programs tomonitor the processes executing on the processor 4001 and any processthat requests access to any hardware and/or software components of thecomputing device 4000 (e.g., ROM 4002, RAM 4003, the removable media4004, the hard drive 4005, the device controller 4007, a networkinterface 4009, a GPS 4011, a Bluetooth interface 4012, a WiFi interface4013, etc.). The computing device 4000 may include one or more outputdevices, such as the display 4006 (e.g., a screen, a display device, amonitor, a television, etc.), and may include one or more output devicecontrollers 4007, such as a video processor. There may also be one ormore user input devices 4008, such as a remote control, keyboard, mouse,touch screen, microphone, etc. The computing device 4000 may alsoinclude one or more network interfaces, such as a network interface4009, which may be a wired interface, a wireless interface, or acombination of the two. The network interface 4009 may provide aninterface for the computing device 4000 to communicate with a network4010 (e.g., a RAN, or any other network). The network interface 4009 mayinclude a modem (e.g., a cable modem), and the external network 4010 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 4000 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 4011, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 4000.

Although FIGS. 4A and 4B show example hardware configurations, one ormore of the elements of the wireless device 400 and/or the computingdevice 4000 may be implemented as software or a combination of hardwareand software. Modifications may be made to add, remove, combine, divide,etc. components of the computing device 4000. Additionally, the elementsshown in FIGS. 4A and 4B may be implemented using basic computingdevices and components that have been configured to perform operationssuch as are described herein. For example, a memory of the computingdevice 4000 may store computer-executable instructions that, whenexecuted by the processor 4001 and/or one or more other processors ofthe computing device 4000, cause the computing device 4000 to performone, some, or all of the operations described herein. Such memory andprocessor(s) may also or alternatively be implemented through one ormore Integrated Circuits (ICs). An IC may be, for example, amicroprocessor that accesses programming instructions or other datastored in a ROM and/or hardwired into the IC. For example, an IC maycomprise an Application Specific Integrated Circuit (ASIC) having gatesand/or other logic dedicated to the calculations and other operationsdescribed herein. An IC may perform some operations based on executionof programming instructions read from ROM or RAM, with other operationshardwired into gates or other logic. Further, an IC may be configured tooutput image data to a display buffer. Components may be implementedusing basic computing devices and components, and the same components(e.g., processor 4001, ROM storage 4002, display 4006, etc.) may be usedto implement any of the other computing devices and components describedherein. For example, the various components described herein may beimplemented using computing devices having components such as aprocessor executing computer-executable instructions stored on acomputer-readable medium, as shown in FIG. 4B. Some or all of theentities described herein may be software based, and may co-exist in acommon physical platform (e.g., a requesting entity may be a separatesoftware process and program from a dependent entity, both of which maybe executed as software on a common computing device).

Base stations, wireless devices, relay nodes, and other communicationdevices may comprise one or more transceivers. A transceiver may be adevice that comprises both a transmitter and receiver. The communicationnetwork may comprise any number and/or type of devices, such as, forexample, computing devices, wireless devices, mobile devices, handsets,tablets, laptops, internet of things (IoT) devices, hotspots, cellularrepeaters, computing devices, and/or, more generally, user equipment.Although one or more of the above types of devices may be referencedherein (e.g., user equipment, wireless device, computing device, etc.),it should be understood that any device herein may comprise any one ormore of the above types of devices or similar devices. The communicationnetwork, and any other network referenced herein, may comprise an LTEnetwork, a 5G network, or any other network for wireless communications.Apparatuses, systems, and/or methods described herein may generally bedescribed as implemented on one or more devices (e.g., a wirelessdevice, base station, eNB, gNB, computing device, etc.), in one or morenetworks, but it will be understood that one or more features and/orsteps may be implemented on any device and/or in any network. As usedthroughout, the term “base station” may comprise one or more of: a basestation, a node, a Node B, a gNB, an eNB, am ng-eNB, a relay node (e.g.,an integrated access and backhaul (IAB) node), a donor node (e.g., adonor eNB, a donor gNB, etc.), an access point (e.g., a WiFi accesspoint), a computing device, a device capable of wirelesslycommunicating, and/or any other device capable of sending and/orreceiving signals. As used throughout, the term “wireless device” maycomprise one or more of: a UE, a handset, a mobile device, a computingdevice, a node, a device capable of wirelessly communicating, or anyother device capable of sending and/or receiving signals. Any referenceto one or more of these terms/devices also considers use of any otherterm/device mentioned above.

FIG. 5 depicts examples of the RM states of a wireless device, such asthe wireless device 100, as observed by the wireless device 100 and AMF155. The top half of FIG. 5 shows RM state transition in the wirelessdevice. Two RM states may be used in a wireless device 100 (and possiblyin the AMF 155) that may reflect the registration status of the wirelessdevice 100 in the selected PLMN. The registration status of the wirelessdevice 100 in the selected PLMN may be RM-DEREGISTERED 500 orRM-REGISTERED 510. In the RM DEREGISTERED state 500, the wireless device100 may not be registered with a network. The wireless device 100context in AMF 155 may not hold valid location or routing informationfor the wireless device 100 so the wireless device 100 may be notreachable by the AMF 155. Some wireless device context may still bestored in the wireless device 100 and the AMF 155. In the RM REGISTEREDstate 510, the wireless device 100 may be registered with the network.In the RM-REGISTERED 510 state, the wireless device 100 may receiveservices that require registration with the network.

The bottom half of FIG. 5 shows RM state transitions in the AMF 155. TwoRM states may be used in the AMF 155 for the wireless device 100 thatreflect the registration status of the wireless device 100 in theselected PLMN. The two RM states that may be used in the AMF 155 for thewireless device 100 in the selected PLMN may be RM-DEREGISTERED 520 orRM-REGISTERED 530. The state of RM-DEREGISTERED 500 in the wirelessdevice 100 may correspond to the state of RM-DEREGISTERED 520 in the AMF155. The state of RM-REGISTERED 510 in the wireless device 100 maycorrespond to the state of RM-REGISTERED 530 in the AMF 155.

FIG. 6 depicts examples of CM state transitions as observed by thewireless device 100 and AMF 155. Connection management CM may comprisethe functions of establishing and releasing a signaling connectionbetween a wireless device 100 and the AMF 155 over N1. This signalingconnection may be used to provide NAS signaling exchange between thewireless device 100 and a core network. The signaling connection maycomprise both the AN signaling connection between the wireless device100 and/or the (R)AN 105 (e.g. RRC connection over 3GPP access) and theN2 connection for this wireless device 100 between the AN and the AMF155. The top half of FIG. 6 shows CM state transitions in the wirelessdevice 100. Two CM states may be used for the NAS signaling connectivityof the wireless device 100 with the AMF 155: CM-IDLE 600 andCM-CONNECTED 610. A wireless device 100 in CM-IDLE 600 state may be inRM-REGISTERED 510 state that may have no NAS signaling connectionestablished with the AMF 155 over N1. The wireless device 100 mayperform cell selection, cell reselection, and PLMN selection. A wirelessdevice 100 in CM-CONNECTED 610 state may have a NAS signaling connectionwith the AMF 155 over N1. RRC inactive state may apply to NG-RAN (e.g.,it applies to NR and E-UTRA connected to 5G CN). The AMF 155 may provide(e.g., based on network configuration) assistance information to the NG(R)AN 105, for example, to assist the NG (R)AN's 105 decision as towhether the wireless device 100 may be sent to RRC inactive state. If awireless device 100 may be CM-CONNECTED 610 with RRC inactive state, thewireless device 100 may resume the RRC connection (e.g., due to uplinkdata pending), may execute a mobile initiated signaling procedure (e.g.,as a response to (R)AN 105 paging), and/or notify the network that ithas left the (R)AN 105 notification area. NAS signaling connectionmanagement may comprise the functions of establishing and releasing aNAS signaling connection. NAS signaling connection establishmentfunction may be provided by the wireless device 100 and the AMF 155 toestablish a NAS signaling connection for a wireless device 100 inCM-IDLE 600 state. The procedure of releasing a NAS signaling connectionmay be initiated by the 5G (R)AN 105 node or the AMF 155.

The bottom half of FIG. 6 shows CM state transitions in the AMF 155. TwoCM states may be used for a wireless device 100 at the AMF 155: CM-IDLE620 and CM-CONNECTED 630. The state of CM-IDLE 600 in the wirelessdevice 100 may correspond to the state of CM-IDLE 620 in the AMF 155.The state of CM-CONNECTED 610 in the wireless device 100 may correspondto the state of CM-CONNECTED 630 in the AMF 155. Reachability managementof the wireless device 100 may detect whether a wireless device 100 maybe reachable and/or provide the wireless device location (e.g., theaccess node in communication with the wireless device) for the networkto reach the wireless device 100. This may be done by paging wirelessdevice 100 and wireless device location tracking. The wireless devicelocation tracking may comprise both wireless device registration areatracking and wireless device reachability tracking. Such functionalitiesmay be either located at a 5GC (e.g., for a CM-IDLE 620 state) or anNG-RAN 105 (e.g., for a CM-CONNECTED 630 state).

The wireless device 100 and the AMF 155 may negotiate wireless device100 reachability characteristics in CM-IDLE 600 and/or 620 states duringregistration and registration update procedures. A variety of wirelessdevice reachability categories may be negotiated between a wirelessdevice 100 and an AMF 155 for CM-IDLE 600 and/or 620 states, such aswireless device 100 reachability providing mobile device terminateddata. The wireless device 100 may be CM-IDLE 600 mode and mobileinitiated connection only (MICO) mode. The 5GC may support a PDUconnectivity service that provides exchange of PDUs between a wirelessdevice 100 and a data network identified by a DNN. The PDU connectivityservice may be supported via PDU sessions that may be established, forexample, after request from the wireless device 100.

A PDU session may support one or more PDU session types. PDU sessionsmay be established (e.g. after wireless device 100 request), modified(e.g. after wireless device 100 and 5GC request) and released (e.g.,after wireless device 100 and 5GC request) using NAS SM signalingexchanged over N1 between the wireless device 100 and the SMF 160. The5GC may be able to trigger a specific application in the wireless device100 (e.g., after a request from an application server). If receivingthat trigger message, the wireless device 100 may pass it to theidentified application in the wireless device 100. The identifiedapplication in the wireless device 100 may establish a PDU session to aspecific DNN.

FIG. 7 shows an example of a QoS flow based framework. A QoS model(e.g., a 5G QoS model) may support the QoS flow based framework. The QoSmodel may support both QoS flows that require a guaranteed flow bit rateand QoS flows that may not require a guaranteed flow bit rate. The QoSmodel may also support reflective QoS. The QoS model may comprise flowmapping or packet marking at the CN_UP 720, AN 710, and/or wirelessdevice 700. Packets may arrive from and/or destined to theapplication/service layer 730 of wireless device 700, CN_UP 720, and/oran AF (e.g., the AF 145). QoS flow may be granular of QoSdifferentiation in a PDU session. A QoS Flow IDQFI may be used toidentify a QoS flow in a 5G system. User plane traffic with the same QFIwithin a PDU session may receive the same traffic forwarding treatment.The QFI may be carried in an encapsulation header on N3 (and N9), forexample, without any changes to an end-to-end packet header. The QFI maybe used with PDUs having different types of payload. The QFI may beunique within a PDU session.

The QoS parameters of a QoS flow may be provided to the (R)AN as a QoSprofile over N2 at a PDU session or at a QoS flow establishment, and anNG-RAN may be used, for example, if the user plane may be activated. Adefault QoS rule may be utilized for every PDU session. An SMF (e.g.,SMF 160) may allocate the QFI for a QoS flow and may derive its QoSparameters from the information provided by the PCF. The SMF 160 mayprovide the QFI together with the QoS profile containing the QoSparameters of a QoS flow to the (R)AN 710. QoS flow may be granular forQoS forwarding treatment in a system (e.g., a 5GS). Traffic mapped tothe same QoS flow may receive the same forwarding treatment (e.g.,scheduling policy, queue management policy, rate shaping policy, RLCconfiguration, and/or the like). Providing different QoS forwardingtreatment may require separate QoS flow. A QoS indicator may be used asa reference to a specific QoS forwarding behavior (e.g., packet lossrate, and/or packet delay budget) to be provided to a QoS flow. This QoSindicator may be implemented in the access network by the 5QIreferencing node specific parameters that control the QoS forwardingtreatment (e.g., scheduling weights, admission thresholds, queuemanagement thresholds, link layer protocol configuration, and/or thelike.).

One or more devices (e.g., a 5GC) may support edge computing and mayprovide operators and/or third party services to be hosted close to thewireless device access point of attachment. The one or more devices(e.g., a 5GC) may select a UPF 110 close to the wireless device 100 andmay execute the traffic steering from the UPF 110 to the LADN via a N6interface. This selecting a UPF 110 close to the wireless device may bebased on the wireless device subscription data, wireless devicelocation, the information from application function AF 145, policy,and/or other related traffic rules. The one or more devices (e.g., a5GC) may expose network information and capabilities to an edgecomputing application function. The functionality support for edgecomputing may comprise local routing where the one or more devices(e.g., a 5GC) may select UPF 110 to route the user traffic to the LADN,traffic steering where the one or more devices (e.g., a 5GC) selects thetraffic to be routed to the applications in the LADN, session andservice continuity to provide wireless device 100 and applicationmobility, user plane selection and reselection (e.g., based on inputfrom application function), network capability exposure where the one ormore devices (e.g., a 5GC) and application function may provideinformation to each other via NEF, QoS and charging where PCF mayprovide rules for QoS control and charging for the traffic routed to theLADN, and/or support of local area data network where the one or moredevices (e.g., a 5GC) may provide support to connect to the LADN in acertain area where the applications are deployed.

An example system (e.g., a 5GS) may be a 3GPP system comprising of 5Gaccess network 105, 5GC and a wireless device 100, and/or the like.Provided NSSAI may be an NSSAI provided by a serving PLMN, for example,during a registration procedure, indicating the NSSAI provided by thenetwork for the wireless device 100 in the serving PLMN for the currentregistration area. A periodic registration update may be wireless device100 re-registration at expiry of a periodic registration timer. Arequested NSSAI may be a NSSAI that the wireless device 100 may provideto the network. A service-based interface may represent how a set ofservices may be provided/exposed by a given NF.

A PDU connectivity service may provide exchange of PDUs between awireless device 100 and a data network. PDU session may be anassociation between a wireless device 100 and a data network, DN thatprovides a PDU connectivity service. The type of association may be IP,Ethernet, or unstructured. Service continuity may comprise anuninterrupted user experience of a service, for example, if the IPaddress and/or anchoring point change. Session continuity may comprisethe continuity of a PDU session. For a PDU session of an IP typesession, continuity may indicate that the IP address may be preservedfor the lifetime of the PDU session. An uplink classifier may be a UPFfunctionality that aims at diverting uplink traffic, for example, basedon filter rules provided by SMF, towards a data network.

The system architecture may support data connectivity and servicesenabling deployments to use techniques such as, but not limited to,network function virtualization and/or software defined networking. Thesystem architecture may leverage service-based interactions betweencontrol plane (CP) network functions where identified. In systemarchitecture, separation of the user plane (UP) functions from thecontrol plane functions may be considered. A system may provide anetwork function to interact with other NF(s) directly if required. Asystem may reduce dependencies between the access network (AN) and thecore network (CN). The architecture may comprise a convergedaccess-agnostic core network with a common AN-CN interface thatintegrates different 3GPP and non-3GPP access types. A systemfurthermore may support a unified authentication framework, statelessNFs (e.g., where the compute resource may be decoupled from the storageresource), capability exposure, and/or concurrent access to local andcentralized services. UP functions may be deployed close to the accessnetwork, for example, to support low latency services and access toLADNs.

A system may support roaming with both home routed traffic as well aslocal breakout traffic in the visited PLMN. An example architecture maybe service-based and the interaction between network functions may berepresented in a variety of ways. FIG. 1 shows an example service-basedrepresentation, where network functions within the control plane mayprovide other authorized network functions to access their services.This service-based representation shown in FIG. 1 may also comprisepoint-to-point reference points where necessary. FIG. 2 shows an examplereference point representation, showing the interaction between the NFservices in the network functions described by point-to-point referencepoint (e.g., N11) between any two network functions.

Establishment of user plane connectivity to a data network via a networkslice instance(s) may comprise performing an RM procedure, for example,to select an AMF 155 that supports the required network slices, andestablishing one or more PDU session(s) to the required data network viathe network slice instance(s). The set of network slices for a wirelessdevice 100 may be changed, for example, if the wireless device 100 maybe registered with a network. The set of network slices for the wirelessdevice 100 may be initiated by the network or the wireless device 100.

FIGS. 8A and 8B show connection, registration, and mobility managementprocedures. These procedures are described, for example, in “5G;Procedures for the 5G System,” ETSI TS 123 502 version 15.2.0, also 3GPPTS 23.502 version 15.2.0 Release 15, dated June 2018 and published bythe European Telecommunications Standards Institute.

At step 801 (in FIG. 8A), a wireless device (e.g., wireless device 100)may send a message comprising a registration request to a (R)AN (e.g.,(R)AN 105). At step 802, the (R)AN 105 may perform an AMF selection. Atstep 803, the (R)AN 105 may send a message comprising the registrationrequest to a new AMF (e.g., New AMF 155-1). At step 804, the New AMF155-1 may send, to an old AMF (e.g., Old AMF 155-2), a messagecomprising an indication of a context transfer (e.g.,Namf_Communication_UEContextTransfer). At step 805, the Old AMF 155-2may send, to the Old AMF 155-1, a response message comprising a contexttransfer response (e.g., Namf_Communication_UEContextTransfer response).At step 806, the New AMF 155-1 may send, to the wireless device 100, amessage comprising an identity request. At step 807, the wireless device100 may send, to the New AMF 155-1, a message comprising an identityresponse. At step 908, the New AMF 155-1 may perform an AUSF selection.At step 809, authentication and/or security procedures may be performedbetween the wireless device 100 and the New AMF 155-1, between the NewAMF 155-1 and a AUSF (e.g., AUSF 150), and/or between the AUSF 150 and aUDM (e.g., UDM 140). At step 810, the New AMF 155-1 may send, to the OldAMF 155-2, a message comprising a registration completion notification(e.g., Namf_Communication_(—) RegistrationCompleteNotify). At step 811,messages comprising identity requests and/or responses may becommunicated between the wireless device 100 and the New AMF 155-1. Atstep 812, the New AMF 155-1 may send to an EIR, and/or the EIR may sendto the AMF 155-1, one or more messages associated with an identity check(e.g., N5g-eir_MEIdentityCheck_Get).

At step 813 (in FIG. 8B), the New AMF 155-1 may perform a UDM selection.At step 814 a, the New AMF 155-1 may send, to the UDM 140, a messagecomprising a context management registration (e.g.,Nudm_UEContextManagement_Registration). The UDM 140 may send, to the NewAMF 155-1, a message comprising a response to the context managementregistration. At step 814 b, the UDM 140 may send, to the New AMF 155-1,a message comprising a notification for a subscription data update(e.g., Nudm_SubscriptionDate_UpdateNotify). At step 814 c, the UDM 140may send, to the Old AMF 155-2, a message comprising a notification of acontext management removal (e.g.,Nudm_UEContextManagement_RemoveNotify). At step 815, the New AMF 155-1may perform a PCF selection. At step 816, the New AMF 155-1 may send, toa PCF (e.g., PCF 135), a message comprising policy control or policycreation (e.g., Npcf_PolicyControl_PolicyCreate). The PCF 135 may send aresponse to the New AMF 155-1. At step 817, the New AMF 155-1 may send,to an SMF (e.g., SMF 160), a message comprising an event exposurenotification (e.g., Namf_EventExposure_Notify(UE Reachability state withPDU status)). At step 818, the New AMF 155-1 may send, to a N3IWF, amessage comprising an N2 request. At step 819, the N3IWF may send, tothe New AMF 155-1, a message comprising an N2 response. At step 820, theOld AMF 155-2 may send, to the PCF 135, a message comprising a policycontrol and/or policy deletion (e.g., Ncpf_PolicyControl_PolicyDelete).The PCF 135 may send a response to the Old AMF 155-2. At step 821, theNew AMF 155-1 may send, to the wireless device 100, a message comprisinga registration acceptance (e.g., Registration Accept). At step 822, thewireless device 100 may send, to the New AMF 155-1, a message comprisinga registration completion (e.g., Registration Complete). Steps indicatedby dashed lines (e.g., steps 806-813, 815-820, and 821) may be optional.

FIG. 9 shows an example of control plane interfaces for network slicing.Control plane network functions (CP NFs) and user plane networkfunctions (UP NFs) are shown in FIG. 9 for slice A, slice B, and sliceC. One or more (R)AN or core base stations may use a slice routing andselection function (SSF) 901 to link radio access bearer(s) of awireless device with the corresponding core network instance(s). Thesubscriber repository 902 may contain subscriber profiles that may beused for authorization. The subscriber repository 902 may also includeuser identities and corresponding long-term credentials forauthentication. The (R)AN 903 may appear as one RAT+PLMN to a wirelessdevice and an association with network instance may be performed by thenetwork internally. The network slices may not be visible to thewireless device. Common CP NFs 904 may be the CP entry function, whichmay include the mobility management function, authentication function,and/or NAS proxy function. The common CP may be shared parts amongdifferent slices. If different types of network slice perform thesharing, the required common CP function may be different for each typeof network slice.

FIG. 10 shows an example depicting wireless device 1 1004, wirelessdevice 2 1005, and wireless device 3 1003 that are assigned to a corepart of network slice instances (NSI). Wireless device 1 1004, wirelessdevice 2 1005 and wireless device 3 1003 are connected to specific corenetwork functions via (R)AN 1002. The core network portion of thenetwork slice may share some network functions with other core networkportions of network slices that serve the same wireless device,including the NG1 and NG2 terminations, in the common control networkfunctions (CCNF). As shown in FIG. 10, wireless device 1 1004 andwireless device 3 1003 may be assigned to common CP NF1 1001 and havethree slices accessing multiple core network slice instances (NSIs) andtherefore multiple slice-specific core network functions. However, itshould be noted that any number of core network slice instances may beutilized. Wireless device 2 1005 may be associated with one NSI and maybe assigned to different Common CP NF 2 1006 (e.g. after the wirelessdevices attach has occurred).

The core network instances may be set up to provide a wireless device toobtain services from multiple network slices of one network operatorsimultaneously. A single set of CP functions that are in common amongcore network instances may be shared across multiple core networkinstances. UP functions and other CP functions that are not in commonmay reside in their respective core network instances, and may be notshared with other core network instances. A slice instance ID may be anidentifier of a network slice instance and may be used as an indicatorby the network to select the corresponding slice for a wireless device.A CP-NF ID may be an identifier of a control plane network functioninstance.

FIG. 11 shows an example depicting a network slice architecture with twogroups-common CP NFs and dedicated CP NFs. The NSSF 1101 may be commonto network slices in the PLMN and may realize the slice selectionfunction for both groups. The NSSF 1101 may store the mappinginformation between slice instance ID and NF ID (and/or NF address). TheNSSF 1101 may have connection with the subscriber repository 1102 to getwireless device subscribed slice instance IDs corresponding to currentPLMN. NSSF 1101 may obtain network slice selection policy informationfrom a policy function. CP-NF ID and/or address may be determined by theNSSF 1101 based on slice instance ID, wireless device subscribedinformation, and/or network slice selection policy. NSSF may respond thespecific CP-NF ID/address corresponding to the slice instance ID of the(R)AN 1103. The NSSF 1101 may be located in the core network, which maybe useful for the interaction and mapping update between the NSSF 1101and subscriber repository 1102. This may make the management of themapping between Slice Instance ID and NF ID/address in a centralizedway. The (R)AN 1103 may act as a routing function to link the wirelessdevice with the appropriate CN part of network slice. The (R)AN 1103 maystore the mapping between the Slice Instance ID and NF ID. The Common CPNFs 1104 may be used for multiple slices with wireless devicessimultaneously connected. A wireless device may access multiple networkslices at the same time. The Common CP NFs 1104 may have common set ofNFs that may be flexibly expanded with additional NFs per slicerequirement.

A wireless device may be slice-provided. If so, there may be one or moreinstances for the attach procedure as described herein. If wirelessdevice attaches without Slice Instance ID, the wireless device may ormay not take some assistant parameters (e.g. service type), the wirelessdevice may or may not take some assistant parameters (e.g. servicetype). The (R)AN may forward the attach request to NSSF 1101. NSSF 1101may check with subscription data and network slice selection policyand/or provide a response with a predefined/default Slice Instance ID tothe wireless device. If a wireless device attaches with a Slice InstanceID, the (R)AN 1103 may not know the corresponding slice. The (R)AN 1103may forward the wireless device request signaling to NSSF 1101 and NSSF1101 may respond with specific CP-NF ID/address corresponding to theSlice Instance ID. The (R)AN 1103 may route the attach request to thespecific CP-NF. If a wireless device attaches with a Slice Instance ID,the (R)AN 1103 may have the related mapping between the Slice InstanceID carried by the wireless device and CP-NF ID. The attach request maybe routed to the specific CP-NF in the core network.

FIG. 12 shows an example diagram depicting multiple slices per wirelessdevice. The network slice instances may be independent and they may notshare any CP or UP functions. The network slice instances may sharecommon databases such as the subscription database and/or policydatabases. Network slices instances may communicate via the NGsinterface. Each network slice instance may have a unique slice identitythat may be resolved to an IP address for communication via NGs.Wireless device 1201 may be simultaneously attached to multiple networkslice instances. One of these slices may be the primary network slice1202 for the wireless device and all the others may be secondary networkslices 1203 for the wireless device. The first attach performed by thewireless device may be called initial attach and attaches the wirelessdevice 1201 to the primary network slice 1202, and a subsequent attachmay be called additional attach and attaches the wireless device to asecondary network slice 1203.

A Network Slice may include the Core Network CP functions, Core NetworkCP functions, a 5G Radio Access Network, and/or the N3IWF functions tothe non-3GPP Access Network. Network slices may differ for supportedfeatures and network functions implementation. The operator may deploymultiple Network Slice instances delivering the same features but fordifferent groups of wireless devices. The instances may deliver adifferent committed service and/or may be dedicated to a customer. TheNSSF may store the mapping information between slice instance ID and NFID (or NF address). A single wireless device may simultaneously beserved by one or more network slice instances via a 5G-AN. A singlewireless device may be served by k network slices (e.g. k=8, 16, etc.)at a time. An AMF instance serving the wireless device logically belongsto a Network Slice instances serving the wireless device. A PDU sessionmay belong to one specific network slice instance per PLMN. Differentnetwork slice instances may not share a PDU session. Different slicesmay have slice-specific PDU sessions using the same DNN. An S-NSSAI(Single Network Slice Selection Assistance information) may identify aNetwork Slice. An S-NSSAI may be included of a slice/service type (SST)(which may refer to the expected Network Slice behavior in terms offeatures and services) and/or a slice differentiator (SD). A slicedifferentiator may be optional information that complements theslice/service type(s) to provide further differentiation for selecting anetwork slice instance from potentially multiple network slice instancesthat comply with the indicated slice/service type. This information maybe referred to as SD. The same Network Slice instance may be selectedemploying different S-NSSAIs. The CN part of a Network Slice instance(s)serving a wireless device may be selected by CN.

Subscription data may comprise the S-NSSAI(s) of the Network Slices towhich the wireless device subscribes. One or more S-NSSAIs may be markedas default S-NSSAI (e.g. k=8, 16, etc.). The wireless device maysubscribe to more than eight S-NSSAI. A wireless device may beconfigured by the HPLMN with a configured NSSAI per PLMN. The wirelessdevice may obtain from the AMF a Provided NSSAI for this PLMN (e.g.after successful completion of a wireless device registrationprocedure), which may comprise one or more S-NSSAIs. The Provided NSSAImay take precedence over the configured NSSAI for this PLMN. Thewireless device may use the S-NSSAIs in the Provided NSSAI correspondingto a Network Slice for the subsequent Network Slice selection relatedprocedures in the serving PLMN. The establishment of user planeconnectivity to a data network via a network slice instance(s) maycomprise performing a RM procedure to select an AMF that supports therequired Network Slices and/or establishing one or more PDU session tothe required Data network via the Network Slice Instance(s). If awireless device registers with a PLMN, if the wireless device for thisPLMN has a configured NSSAI or a provided NSSAI, the wireless device mayprovide to the network, in the Radio Resource Control (RRC) and/or NAS,a Requested NSSAI containing the S-NSSAI(s) corresponding to theslice(s) to which the wireless device attempts to register in additionto the temporary user ID, if one was assigned to the wireless device.The Requested NSSAI may be the configured-NSSAI and/or theProvided-NSSAI. If a wireless device registers with a PLMN, if for thisPLMN the wireless device has no configured NSSAI or Provided NSSAI, the(R)AN may route NAS signaling from/to this wireless device to/from adefault AMF.

The network, based on local policies, subscription changes, and/orwireless device mobility, may change the set of permitted NetworkSlice(s) to which the wireless device may be registered. The network mayperform such change during a registration procedure and/or trigger anotification towards the wireless device of the change of the supportedNetwork Slices using an RM procedure, which may trigger a registrationprocedure. The Network may provide the wireless device with a newProvided NSSAI and Tracking Area list. During a Registration procedurein a PLMN, if the network decides that the wireless device should beserved by a different AMF based on Network Slice(s) features, the AMFthat first received the Registration Request may redirect theRegistration request to another AMF via the (R)AN or via directsignaling between the initial AMF and the target AMF.

The network operator may provision the wireless device with a networkslice selection policy (NSSP). The NSSP may comprise one or more NSSPrules. An NSSP rule may associate an application with a certain S-NSSAI.A default rule which matches one or more applications to an S-NSSAI mayalso be comprised. If a wireless device application associated with aspecific S-NSSAI requests data transmission, a variety of actions may beperformed. If the wireless device has one or more PDU sessionsestablished corresponding to the specific S-NSSAI, the wireless devicemay route the user data of this application in one of these PDUsessions, unless other conditions in the wireless device prohibit theuse of these PDU sessions. If the application provides a DNN, thewireless device may consider also this DNN to determine which PDUsession to use. If the wireless device does not have a PDU sessionestablished with this specific S-NSSAI, the wireless device may requesta new PDU session corresponding to this S-NSSAI and with the DNN thatmay be provided by the application. In order for the (R)AN to select aproper resource for supporting network slicing in the (R)AN, (R)AN maybe aware of the Network Slices used by the wireless device.

The AMF may select a SMF in a Network Slice instance based on S-NSSAI,DNN and other information, such as wireless device subscription and/orlocal operator policies, if the wireless device triggers theestablishment of a PDU session. The selected SMF may establish a PDUsession based on S-NSSAI and DNN. In order to support network-controlledprivacy of slice information for the slices the wireless device accessesif the wireless device may be aware or configured that privacyconsiderations apply to NSSAI, the wireless device might not compriseNSSAI in NAS signaling unless the wireless device has a NAS securitycontext and/or the wireless device might not comprise NSSAI inunprotected RRC signaling. For roaming scenarios, the Network Slicespecific network functions in VPLMN and HPLMN may be selected based onthe S-NSSAI provided by the wireless device during PDU connectionestablishment. If a standardized S-NSSAI may be used, selections ofslice specific NF instances may be done by each PLMN based on theprovided S-NSSAI. Additionally, the VPLMN may map the S-NSSAI of HPLMNto a S-NSSAI of VPLMN based on roaming agreement (comprising mapping toa default S-NSSAI of VPLMN). The selection of slice specific NF instancein VPLMN may be based on the S-NSSAI of VPLMN and/or the S-NSSAI ofHPLMN.

The 5G system may provide an operator to configure the information thatmay associate a service to a network slice. Operators may use networkslicing implementation to support multiple third parties (e.g.enterprises, service providers, content providers, etc.) that mayrequire similar network characteristics. A business application layermay contain specific applications and services of the operator,enterprise, verticals, and/or third parties that utilize a 5G network.The interface to the end-to-end management and orchestration entity mayprovide dedicated network slices for an application and/or a mapping ofan application to existing network slices. A 5G system may supportnetwork slicing for specific applications. Legacy solutions may notsupport application initiated network slicing. This may cause aninterworking problem between the wireless device and the applicationserver for different vendors that may have different implementations fora network slicing initiation. A variety of mechanisms may be providedfor an application to trigger the establishment of dedicated networkslices.

If a wireless device has registered to a 5G network, both the wirelessdevice and network may initiate the PDU sessions. For the networkinitiated PDU session establishment procedure, the network may send adevice trigger message to the application(s) on the wireless deviceside. The trigger payload may be comprised in device trigger requestmessage containing the information on which application on the wirelessdevice side may be expected to trigger the PDU session establishmentrequest. Based on that information, the application(s) on the wirelessdevice may trigger the PDU session establishment procedure. Anapplication function AF may transmit the network slicing relatedinformation to the PCF. AF may transmit to PCF a request. The requestmay comprise at least information to identify the traffic to be routed.The traffic may be identified in the AF request by: a DNN and possiblyslicing information (S-NSSAI) and/or an AF-Service-Identifier. If the AFprovides an AF-Service-Identifier, such as an identifier of the serviceon behalf of which the AF may be issuing the request, the 5GC may mapthis identifier into a target DNN and slicing information (S-NSSAI). Oneor more of the following may be implemented to initiate and/or establisha new slice by an application: the PCF and/or NEF may receive from AF amessage comprising network slicing information, the PCF and/or NEF maytrigger the network slicing establishment procedure, and/or the AF maybe the application function of the operator or a third party applicationserver (e.g. vertical industrial application server). If the third partyapplication does not support the AF, the third party application mayrequest the AF as a sponsor, which may be transparent to the PCF and/orNEF.

The network slicing information may comprise a variety of informationelements. Network slicing required information indicates the applicationrequires a dedicated network slice. Without this indication, theoperator network might not know whether to reuse the current slice orestablish a new one. Required bandwidth information (e.g. minimalbandwidth) for the network slice may describe the bandwidth to supportthe service and/or a measure of priority for the bandwidth (e.g., thebandwidth may be guaranteed for medical applications). Provided latencyinformation for the network slice may describe the particular servicelevel needed to support the service (e.g., for the time sensitiveapplication Video, VoIP etc.). Priority information for the networkslice may be used to allocate priority for network resources (e.g.,higher priority network slices (e.g., emergency services) may have thepriority on the resource allocation) and/or preempt existing lowerpriority network slices if the requested resource may be limited. Thirdparty ID and third party charging information may be used to identify athird party and/or indicate that the service may be free of charge forthe wireless device but incur a charge for the third party (and viceversa). S-NSSAI or an AF-Service-Identifier information may comprise aSlice/Service type (SST) and a Slice Differentiator (SD) that mayindicate expected Network Slice behavior in terms of features andservices. The AF-Service-Identifier may be the identifier of theservice.

If the PDU session is also required at the same time, the AF may alsoprovide the following information to the PCF or NEF: the service dataflow information may be IP 5-tuple (i.e. source IP address, destinationIP address, source port number, destination port number and the protocolin use) or application identifier (e.g., Skype, video conferencingapplications, etc.), the user identity may be the wireless device IPv4address or IPv6 prefix, the wireless device NAI, etc., and/or the APN IDmay be to identify a specific PDN.

There may be a variety of roaming scenarios including, e.g. if the AFmay be located in the home PLMN (HPLMN) or if the AF may be located inthe visited PLMN (VPLMN). One or more of the following may beimplemented to initiate and/or establish a new slice by an application:the HPCF/VPCF and/or HNEF/VNEF may receive from HAF/VAF a messageincluding network slicing information, the HPCF/VPCF and/or HNEF/VNEFmay trigger the network slicing establishment procedure, and the HAF/VAFmay be the application function of the operator or a third partyapplication server (e.g. vertical industrial application server). If thethird party application does not support the AF, the third partyapplication may request the HAF/VAF as a sponsor, which may betransparent to the HPCF/VPCF and/or HNEF/VNEF. A HAF may initiate andestablish a new network slice, and a network slice ID may be allocatedby a VPCF.

FIG. 13A and FIG. 13B show example methods for service requests. At step1301, a wireless device may send, to a (R)AN 105, a service request. Theservice request may comprise a NAS service request. A service requestprocedure may be triggered by the wireless device 100. The servicerequest procedure may be used by the wireless device 100 in a CM-IDLEstate, for example, to request the establishment of a secure connectionto an AMF 155. The service request procedure may be used to activate auser plane connection for an established PDU session. The servicerequest procedure may be triggered by the wireless device 100 or byanother device (e.g., a 5GC). The service request procedure may be usedif the wireless device 100 is in CM-IDLE and/or in CM-CONNECTED. Theservice request procedure may allow for selectively activating userplane connections for one or more established PDU sessions.

A wireless device in CM IDLE state may initiate the service requestprocedure, for example, to send uplink signaling messages, for userdata, as a response to a network paging request, and/or the like. Atstep 1302, the (R)AN 105 may send, to an AMF 155, a message. The messagemay comprise an N2 message. The message may comprise the service requestmessage received from the wireless device 100 at step 1301. At step1303, the AMF 155 may send one or more messages, for example, one ormore authentication and/or security messages. The AMF 155 may performauthentication, for example, after or in response to receiving theservice request message. The wireless device 100 and/or another device(e.g., in a network, such as shown in FIG. 1) may send signalingmessages, for example, after or in response to the establishment of thesignaling connection to the AMF 155. Signaling messages may comprise,for example, a PDU session establishment from the wireless device 100 toa SMF 160, via the AMF 155.

The AMF 155 may respond to a service request with a service acceptmessage, for example, to synchronize PDU session status between thewireless device 100 and other devices in a network (e.g., such as shownin FIG. 1). The AMF 155 may respond, to the wireless device 100, bysending a service reject message, for example, if the service requestmay not be accepted by one or more devices in the network. The servicereject message may include an indication and/or cause code requestingthe wireless device 100 to perform a registration update procedure. Oneor more devices in the network may take further actions for a servicerequest that may be due to user data, for example, if user planeconnection activation may not be successful. More than one UPF (e.g.,old UPF 110-2 and PDU session anchor PSA UPF 110-3, in FIG. 13A and FIG.13B) may be used for a service request procedure.

The wireless device 100 may send, to a (R)AN 105, an AN message. The ANmessage may comprise AN parameters, mobility management, MM NAS ServiceRequest (e.g., a list of PDU sessions to be activated, a list of allowedPDU sessions, security parameters, PDU session status). The list of PDUsessions to be activated may be provided by the wireless device 100, forexample, if the wireless device 100 re-activates the PDU session(s). Thelist of allowed PDU sessions may be provided by the wireless device 100,for example, if the service request is a response to a paging or a NASnotification. The list of allowed PDU sessions may identify the PDUsessions that may be transferred and/or associated to the access onwhich the service request may be sent. The AN parameters may include aselected PLMN ID and/or an establishment cause, for example, for anNG-RAN. The establishment cause may provide a reason for requesting theestablishment of an RRC connection. The wireless device 100 may send aNAS service request message towards the AMF 155 (e.g., at step 1301).The NAS service request message may be encapsulated in an RRC message tothe RAN 105.

If the service request may be triggered for user data, the wirelessdevice 100 may identify, using the list of PDU sessions to be activated,the PDU session(s) for which the UP connections are to be activated inthe NAS service request message. If the service request may be triggeredfor signaling, the wireless device 100 may not identify any PDUsession(s). If this procedure may be triggered for a paging response,and/or if the wireless device 100 may have at the same time user data tobe transferred, the wireless device 100 may identify the PDU session(s)having UP connections that may be activated in an MM NAS service requestmessage. The wireless device may identify the PDU session by the list ofPDU sessions to be activated. The wireless device 100 may not identifyany PDU session(s) in the service request message for paging response.

The NAS service request message may identify in the list of allowed PDUsessions the list of PDU sessions associated with the non-3GPP accessthat may be re-activated over 3GPP, for example, if the service requestover 3GPP access may be triggered after or in response to a pagingindicating non-3GPP access. The PDU session status may indicate the PDUsessions that may be available in the wireless device 100. For example,the wireless device 100 may not trigger the service request procedurefor a PDU session corresponding to a local area data network (LADN) ifthe UE 100 may be outside the area of availability of the LADN. Thewireless device 100 may not identify such PDU session(s) in the list ofPDU sessions to be activated, for example, if the service request may betriggered for other reasons.

The (R)AN 105 may send (e.g., at step 1302), to the AMF 155, an N2message comprising N2 parameters, MM NAS service request, and/or thelike. The AMF 155 may reject the N2 message, for example, if it may notbe able to handle the service request. The N2 parameters may include the5G-GUTI, selected PLMN ID, location information, RAT type, establishmentcause, and/or the like, for example, if an NG-RAN may be used. A 5G-GUTIor other device may be obtained, for example, via an RRC procedure. The(R)AN 105 may select the AMF 155 according to the 5G-GUTI or otherdevice. The location information and RAT type may relate to the cell inwhich the wireless device 100 may be camping. The AMF 155 may initiate aPDU session release procedure in the network (e.g., based on the PDUsession status) for the PDU sessions comprising PDU session ID(s) thatmay be indicated by the wireless 100 as not being available.

At step 1303, the AMF 155 may initiate a NAS authentication and/orsecurity procedure, for example, if the service request was not sentintegrity protected and/or if integrity protection verification failed.The wireless device 100 and the network may exchange NAS signaling, forexample, after or in response to a successful establishment of thesignaling connection (e.g., if the wireless device 100 triggers theservice request to establish a signaling connection).

At step 1304, the AMF 155 may send, to the SMF 160, a PDU session updatecontext request (e.g., Nsmf_PDUSession_UpdateSMContext Request). The PDUsession update may comprise one or more of: PDU session ID(s), cause(s),wireless device 100 location information, access type, and/or the like.

A PDU session update (e.g., Nsmf_PDUSession_UpdateSMContext Request) maybe invoked by the AMF 155, for example, if the wireless device 100identifies PDU session(s) to be activated in a service request message(e.g., the NAS service request message at step 1301). The PDU sessionupdate (e.g., Nsmf_PDUSession_UpdateSMContext Request) may be triggeredby the SMF 160, for example, if the PDU session(s) identified by thewireless device 100 may correlate to PDU session ID(s) other than thePDU session triggering the procedure. The PDU session update (e.g.,Nsmf_PDUSession_UpdateSMContext Request) may be triggered by the SMF160, for example, if the current wireless device 100 location may beoutside the area of validity for the N2 information provided by the SMF160 during a network triggered service request procedure. The AMF 155may not send the N2 information provided by the SMF 160 during thenetwork triggered service request procedure.

The AMF 155 may determine the PDU session(s) to be activated. At step1304, the AMF 155 may send, to the SMF 160, the PDU session update(e.g., an Nsmf_PDUSession_UpdateSMContext Request). The SMF 160 may beassociated with a PDU session(s) with a parameter (e.g., a causeindication) set to indicate an establishment of user plane resources forthe PDU session(s).

The AMF 155 may notify the SMF 160 that the user plane for the PDUsession may not be re-activated, for example, if the service requestprocedure may be triggered after or in response to paging (which mayindicate non-3GPP access) and/or if the list of allowed PDU sessionsprovided by the wireless device 100 does not include the PDU session forwhich the wireless device 100 was paged. The service request proceduremay succeed without re-activating the user plane of any PDU sessions.The AMF 155 may notify the wireless device 100 that the service requestprocedure may succeed without re-activating the user plane of any PDUsessions.

The SMF 160 may determine that the wireless device 100 may be outsidethe area of availability of the LADN, for example, if the PDU session IDmay correspond to a LADN and/or based on the wireless device 100location reporting from the AMF 155. The SMF 160 may determine (e.g.,based on one or more local policies) to keep the PDU session, forexample, if the SMF 160 determines that the wireless device 100 isoutside the area of availability for the LADN. The SMF 160 may rejectthe activation of a user plane connection for the PDU session. The SMF160 may inform the AMF 155 about the rejection of the activation of auser plane connection for the PDU session. The SMF 160 may notify theUPF 110 that originated the data notification to discard downlink datafor the PDU sessions and/or to not provide further data notificationmessages, for example, if the service request procedure is triggered bya network triggered service request. The SMF 160 may respond to the AMF155 with an appropriate reject cause and the user plane activation ofPDU session may be stopped. The SMF 160 may determine (e.g., based onone or more local policies) to release the PDU session for example, ifthe SMF 160 determines that the wireless device 100 is outside the areaof availability for the LADN. The SMF 160 may locally release the PDUsession. The SMF 160 may inform the AMF 155 that the PDU session may bereleased. The SMF 160 may respond to the AMF 155 with an appropriatereject cause and the user Plane Activation of PDU Session may bestopped.

At step 1305, the SMF 160 may check UPF 110 selection criteria, forexample, if the UP activation of the PDU session may be accepted by theSMF 160. The UP activation of the PDU session may be accepted by the SMF160 based on the location info received from the AMF 155. The UPF 110selection criteria may comprise one or more of: slice isolationrequirements, slice coexistence requirements, a UPF's dynamic load, aUPF's relative static capacity among UPFs supporting the same DNN, UPF110 location available at the SMF 160, wireless device 100 locationinformation, capability of the UPF 110, and/or the functionalityrequired for the particular wireless device 100 session. An appropriateUPF 110 may be selected (e.g., at step 1305) by matching thefunctionality and features required for a wireless device 100, datanetwork name (DNN), PDU session type (e.g., IPv4, IPv6, Ethernet type orunstructured type), and/or, if applicable, the static IP address/prefix,SSC mode selected for the PDU session, wireless device 100 subscriptionprofile in UDM, and/or DNAI (e.g., included in the policy and chargingcontrol (PCC) pules, local operator policies, S-NSSAI, access technologybeing used by the wireless device 100, UPF logical topology, and/or thelike). The UPF selected at step 1305 may determine to perform one ormore of the following: continue using the current UPF(s); select a newintermediate UPF 110 (or add/remove an intermediate UPF 110); triggerre-establishment of the PDU session to perform relocation of the UPF 110acting as a PDU session anchor. The UPF 110 may select a newintermediate UPF 110 (or add/remove an intermediate UPF 110), forexample, if the wireless device 100 has moved out of the service area ofthe UPF 110 that was previously connecting to the AN. The UPF 110 mayselect a new UPF 110 while maintaining the UPF(s) acting as PDU sessionanchor. The UPF 110 may trigger re-establishment of the PDU session toperform relocation of the UPF 110 acting as a PDU session anchor, forexample, if the wireless device 100 has moved out of the service area ofthe anchor UPF 110 that is connecting to the (R)AN 105.

At step 1306 a, the SMF 160 may send, to the UPF 110 (e.g., newintermediate UPF 110) an N4 session establishment request. An N4 sessionestablishment request message may be sent to the new UPF 110, which mayprovide packet detection, data forwarding, and/or enforcement andreporting rules to be installed on the new intermediate UPF. The SMF 160may send the N4 session establishment request message, for example, ifthe SMF 160 may select a new UPF 110 to act as intermediate UPF 110-2for the PDU session, and/or if the SMF 160 may select to insert anintermediate UPF for a PDU session that may not have an intermediate UPF110-2. The PDU session anchor addressing information (e.g., on N9) forthe PDU session may be provided to the intermediate UPF 110-2. The SMF160 may include a data forwarding indication, for example, if a new UPF110 is selected by the SMF 160 to replace the old (intermediate) UPF110-2. The data forwarding indication may indicate to the UPF 110 that asecond tunnel endpoint may be reserved for buffered DL data from the oldI-UPF.

At step 1306 b, the new UPF (intermediate) may send to SMF 160 an N4session establishment response message. The UPF 110 may provide DL CNtunnel information for the UPF 110 acting as PDU session anchor and/orUL CN tunnel information (e.g., CN N3 tunnel information) to the SMF160, for example, if the UPF allocates CN tunnel information. The new(intermediate) UPF 110 acting as an N3 terminating point may send DL CNtunnel information for the old (intermediate) UPF 110-2 to the SMF 160,for example, if the data forwarding indication is received. The SMF 160may start a timer. After or in response to an expiration of the timer,the SMF may release the resource in the old intermediate UPF 110-2.

At step 1307 a, the SMF 160 may send, to a PDU session anchor (e.g., PSAUPF 110-3), an N4 session modification request message, for example, ifthe SMF 160 selects a new intermediate UPF 110 for the PDU sessionand/or removes the old I-UPF 110-2. The N4 session modification requestmessage may provide the data forwarding indication and DL tunnelinformation from the new intermediate UPF 110.

The (PSA) UPF 110-3 may begin to send the DL data to the new I-UPF 110as indicated in the DL tunnel information, for example, if the newintermediate UPF 110 is added for the PDU session. The SMF 160 mayinclude the data forwarding indication in the request, for example, ifthe service request is be triggered by a network and the SMF 160 removesthe old I-UPF 110-2 and does not replace the old I-UPF 110-2 with thenew I-UPF 110. The data forwarding indication may indicate to the (PSA)UPF 110-3 that a second tunnel endpoint may be reserved for buffered DLdata from the old I-UPF 110-2. The PSA UPF 110-3 may begin to buffer theDL data it may receive from the N6 interface.

At step 1307 b, the PSA UPF 110-3 (PSA) may send, to the SMF 160, an N4session modification response. The PSA UPF 110-3 may become an N3terminating point and/or the PSA UPF 110-3 may send CN DL tunnelinformation for the old (intermediate) UPF 110-2 to the SMF 160, forexample, if the data forwarding indication is received. The PSA UPF110-3 may send, to the UPF 110, downlink data. The SMF 160 may start atimer. After or in response to an expiration of the timer, the SMF 160may release the resource in old intermediate UPF 110-2 (e.g., ifapplicable).

At step 1308 a, the SMF 160 may send, to the old UPF 110-2(intermediate), an N4 session modification request. The N4 sessionmodification request may comprise, for example, a new UPF 110 address, anew UPF 110 DL tunnel ID, and/or the like. The SMF 160 may send the N4session modification request message to the old (intermediate) UPF 110-2and/or provide the DL tunnel information for the buffered DL data, forexample, if the service request is triggered by a device other than thewireless device 100 (e.g., in a network such shown in FIG. 1) and/or ifthe SMF 160 removes the old (intermediate) UPF 110-2. If the SMF 160allocates a new I-UPF 110, the DL tunnel information may be from the new(intermediate) UPF 110, which may operate as an N3 terminating point. Ifthe SMF 160 does not allocate a new I-UPF 110, the DL tunnel informationmay be from the new UPF (PSA) 110-3, which may operate as an N3terminating point. The SMF 160 may start a timer. The SMF 160 maymonitor the forwarding tunnel, for example, if the timer is running. Atstep 13008 b, the old (intermediate) UPF 110-2 may send, to the SMF 160,an N4 session modification response message.

At step 1309, the old (intermediate) UPF 110-2 may forward its buffereddata to the new (intermediate) UPF 110 operating as an N3 terminatingpoint, for example, if the I-UPF 110-2 is relocated and/or if aforwarding tunnel is established to the new I-UPF 110. At step 1310, theold (intermediate) UPF 110-2 may forward its buffered data to the UPF(PSA) 110-3 which may operate as an N3 terminating point, for example,if the old I-UPF 110-2 is removed and the new I-UPF is not assigned forthe PDU session and/or if a forwarding tunnel is established to the UPF(PSA) 110-3.

At step 1311, the SMF 160 may send, to the AMF 155, an N11 message(e.g., a Nsmf_PDUSession_UpdateSMContext Response). The N11 message maycomprise an N1 SM container (e.g., a PDU session ID and/or a PDU sessionre-establishment indication), N2 SM information (e.g., a PDU session ID,a QoS profile, CN N3 tunnel information, S-NSSAI), and/or causeinformation. The SMF may send the N11 message after or in response toreceiving an Nsmf_PDUSession_UpdateSMContext Request message comprisingcause information (e.g., an establishment of user plane resources). TheSMF 160 may determine whether UPF 110 reallocation may be performed, forexample, based on the wireless device 100 location information, UPF 110service area, and/or operator policies.

At step 1311, the SMF 160 may determine N2 SM information, for example,for a PDU session that the SMF 160 may determine to be served by thecurrent UPF 110 (e.g., PDU session anchor or intermediate UPF). The SMF160 may send a message (e.g., an Nsmf_PDUSession_UpdateSMContextResponse) to the AMF 155 to establish the user plane(s). The N2 SMinformation may comprise information that the AMF 155 may provide to the(R)AN 105. The SMF 160 may reject the activation of UP of the PDUsession, for example, if the SMF 160 determines that a PDU session mayrequire a UPF 110 relocation for a PDU session anchor UPF. The SMF 160may reject the activation of UP of the PDU session, for example, bysending, to the wireless device 100 via the AMF 155, a message (e.g., anNsmf_PDUSession_UpdateSMContext Response) that may comprise an N1 SMcontainer. The N1 SM container may comprise a corresponding PDU sessionID and/or PDU session re-establishment indication.

Upon or after reception of an Namf_EventExposure_Notify message, fromthe AMF 155 to the SMF 160, comprising an indication that the wirelessdevice 100 is reachable (e.g., if the SMF 160 may have pending DL data),the SMF 160 may invoke an Namf_Communication_N1N2MessageTransfer serviceoperation to the AMF 155 to establish the user plane(s) for the PDUsessions. The SMF 160 may resume sending DL data notifications to theAMF 155 (e.g., if the SMF 160 has DL data).

The SMF 160 may send to a message to the AMF 155 to reject theactivation of UP of the PDU session, for example, by including a causein the Nsmf_PDUSession_UpdateSMContext Response. The SMF 160 may sendthe message to reject the activation of UP of the PDU session, forexample, if the PDU session corresponds to a LADN and/or if the wirelessdevice 100 is outside the area of availability of the LADN. The SMF 160may send the message to reject the activation of UP of the PDU session,for example, if the AMF 155 notifies the SMF 160 that the wirelessdevice 100 may be reachable for regulatory prioritized service and/or ifthe PDU session to be activated may not be for a regulatory prioritizedservice. The SMF 160 may send the message to reject the activation of UPof the PDU session, for example, if the SMF 160 decides to perform PSAUPF 110-3 relocation for the requested PDU session.

At step 1312, the AMF 155 may send, to the (R)AN 105, an N2 requestmessage. The N2 request message may comprise, e.g., N2 SM informationreceived from SMF 160, security context, AMF 155 signaling connectionID, handover restriction list, MM NAS service accept, and/or a list ofrecommended cells, TAs, and/or NG-RAN node identifiers. The (R)AN 105may store the security context, AMF 155 signaling connection ID, QoSinformation for the QoS flows of the PDU sessions that may be activatedand N3 tunnel IDs in the wireless device 100 (R)AN 105 context. The MMNAS Service Accept may include PDU session status in the AMF 155. The MMNAS Service Accept may include the PDU session ID and the reason why theuser plane resources may not activated (e.g., LADN not available), forexample, if the activation of UP of a PDU Session is be rejected by theSMF 160. Local PDU session release during the session request proceduremay be indicated to the wireless device 100 via the session status.

In an example, if there are multiple PDU Sessions that may involvemultiple SMFs, the AMF 155 may not wait for responses from all SMFsbefore it may send N2 SM information to the wireless device 100. The AMF155 may wait for all responses from the SMFs before it may send MM NASService Accept message to the wireless device 100.

The AMF 155 may include at least one N2 SM information from the SMF 160,for example, if the service request procedure is triggered for PDUsession user plane activation. The AMF 155 may send additional N2 SMinformation from SMFs in separate N2 message(s) (e.g., N2 tunnel setuprequest), if there is any. The AMF 155 may send one N2 request messageto the (R)AN 105 after all Nsmf_PDUSession_UpdateSMContext responseservice operations from all of the SMFs associated with the wirelessdevice 100 are received, for example, if multiple SMFs are involved inthe service request procedure. The N2 request message may comprise theN2 SM information received in each of theNsmf_PDUSession_UpdateSMContext Responses and PDU Session IDs, forexample, to enable the AMF 155 to associate responses to a relevant SMF160.

The AMF 155 may include information from a list in the N2 request, forexample, if the (R)AN 105 (e.g., NG-RAN) node may provide the list ofrecommended cells, TAs, NG-RAN identifiers during the AN releaseprocedure. The RAN 105 may use this information to allocate the (R)AN105 notification area if the (R)AN 105 determines to enable an RRCinactive state for the wireless device 100. If the AMF 155 receives anindication, from the SMF 160 during a PDU session establishmentprocedure that the wireless device 100 may be using a PDU sessionrelated to latency sensitive services (e.g., for any of the PDU sessionsestablished for the wireless device 100 in which the AMF 155 hasreceived an indication from the wireless device 100 that may support theCM-CONNECTED with RRC Inactive state), then the AMF 155 may include, inthe N2 request, the wireless device 100's RRC inactive assistanceinformation. The AMF 155 may include the wireless device's 100 RRCinactive assistance information, for example, based on a networkconfiguration.

At step 1313, the (R)AN 105 may send, to the wireless device 100, amessage comprising an indication to perform an RRC connectionreconfiguration. The indication to perform an RRC connectionreconfiguration may be based on QoS information for one or more or allof the QoS flows of the PDU sessions in which UP connections and dataradio bearers may be activated. The user plane security may beestablished.

The (R)AN 105 may forward an MM NAS service accept to the wirelessdevice 100, for example, if the N2 request comprises the MM NAS serviceaccept message. The wireless device 100 may locally delete context ofPDU sessions that may not be available in a network (e.g., a 5GC).

The wireless device 100 may initiate PDU session re-establishment forthe PDU session(s) that may be re-established after the service requestprocedure may be complete, for example, if the N1 SM information istransmitted to the wireless device 100 and indicates that some PDUsession(s) may be re-established. After the user plane radio resourcesmay be setup, the uplink data from the wireless device 100 may beforwarded to the (R)AN 105. The (R)AN 105 (e.g., NG-RAN) may send theuplink data to the UPF address and tunnel ID provided. For example, the(R)AN 105 may send the uplink data to the AMF 155, which may then sendthe uplink data to PSA UPF 110-3. The AMF 155 mat send the uplink datato the PSA UPF 110-3 via the UPF 110.

In FIG. 13B, at step 1314, the (R)AN 105 may send, to the AMF 155, an N2request acknowledgement (e.g., N2 SM information). The (R)AN 105 maysend the N2 request acknowledgement after or in response to receivingthe N2 request (e.g., at step 1312). The N2 request acknowledgement maycomprise AN tunnel information, a list of accepted QoS flows for the PDUsessions for which UP connections are activated, and/or a list ofrejected QoS flows for the PDU sessions for which UP connections areactivated. The N2 request message (e.g., at step 1312) may comprise N2SM information, such as AN tunnel information. The (R)AN 105 may respondto the N2 SM information with a separate N2 message (e.g., an N2 tunnelsetup response). The N2 request acknowledgement may include multiple N2SM information and/or information to enable the AMF 155 to associate theresponses to a relevant SMF 160, for example, if multiple N2 SMinformation is included in the N2 request message.

At step 1315, the AMF 155 may send, to the SMF 160, a request message(e.g., Nsmf_PDUSession_UpdateSMContext Request). The request message maycomprise N2 SM information (e.g., AN tunnel information), RAT type) perPDU session. The AMF 155 may forward N2 SM information to the relevantSMF 160, for example, if the AMF 155 receives N2 SM information (e.g.,one or multiple) from the (R)AN 105. The AMF 155 may include thewireless device 100 time zone IE in the request message (e.g.,Nsmf_PDUSession_UpdateSMContext Request), for example, if the wirelessdevice 100 time zone has changed relative to the last reported wirelessdevice 100 time zone.

At step 1316 a, the SMF 160 may initiate a notification about newlocation information to the PCF 135 (if subscribed) by invoking an eventexposure notification operation (e.g., an Nsmf_EventExposure_Notifyservice operation), for example, if a dynamic PCC is deployed. At step1316 b, the PCF 135 may provide updated policies to the SMF 160 byinvoking a policy control update notification message (e.g., anNpcf_SMPolicyControl_UpdateNotify operation).

At step 1317 a, if the SMF 160 selects a new UPF 110 to act asintermediate UPF 110 for the PDU session, the SMF 160 may initiate an N4session modification procedure by sending, to the new I-UPF 110-1, an N4session modification request. The N4 session modification request maycomprise AN tunnel information. At step 1317 b, the new I-UPF 110-1 mayrespond to the N4 session modification request by sending, to the SMF160, an N4 session modification response. The new I-UPF 110-1 mayforward, to the (R)AN 105 and the wireless device 100, downlink data.

At step 1318 a, the SMF 160 may send, to the PSA UPF 110-3, an N4session modification request. At step 1318 b, the PSA UPF 110-3 maysend, to the SMF 160, an N4 session modification response. The PSA UPF110-3 may send, to the (R)AN 105 and/or to the wireless device 100,downlink data. At step 1319, the SMF 160 may send, to the AMF 155, aresponse message (e.g., an Nsmf_PDUSession_UpdateSMContext Response).

At step 1320 a, the SMF 160 may send, to the new (intermediate) I-UPF110-1, a modification request message (e.g., an N4 session modificationrequest), for example, if a forwarding tunnel is established to the new(intermediate) I-UPF 110-1 and/or if a timer that they SMF 160 set forthe forwarding tunnel has expired. The new (intermediate) I-UPF 110-1may operate as an N3 terminating point to release the forwarding tunnel.At step 1321 a, the SMF 160 may send, to the PSA UPF 110-3, amodification request message (e.g., an N4 session modification request).At step 1321 b, the PSA UPF 110-3 may send, to the SMF 160, a responsemessage (e.g., an N4 session modification response).

At step 1322 a, the SMF 160 may send, to the old UPF 110-2, amodification message and/or a release message (e.g., an N4 sessionmodification request and/or an N4 session release request). The SMF 160may send a modification message (e.g., an N4 session modificationrequest) that may comprise AN tunnel information, for example, if theSMF 160 continues using the old UPF 110-2. The SMF 160 may initiate aresource release (e.g., if a timer expires) by sending a release message(e.g., an N4 session release request) to the old intermediate UPF 110-2,for example, if the SMF 160 selects a new UPF 110 to act as anintermediate UPF 110 and/or if the old UPF 110-2 may not be the PSA UPF110-3. The release message may comprise release cause information.

At step 1322 b, the old intermediate UPF 110-2 may send, to the SMF 160,a response message (e.g., an N4 session modification response and/or anN4 session release response). The old UPF 110-2 may acknowledge themessage from step 1322 a, for example, with an N4 session modificationresponse and/or an N4 session release response message to confirm themodification and/or release of resources. The AMF 155 may invoke aservice operation (e.g., Namf_EventExposure_Notify service operation) tonotify the mobility related events after the service request procedureis complete. The AMF 155 may send one or more messages towards the NFsthat may have subscribed for the events. The AMF 155 may invoke theNamf_EventExposure_Notify towards the SMF 160, for example: if the SMF160 had subscribed for the wireless device 100 moving into or out of anarea of interest and the wireless device's 100 current locationindicates that it may be moving into or moving outside of the area ofinterest subscribed; if the SMF 160 had subscribed for LADN DNN and thewireless device 100 may be moving into or outside of an area where theLADN is available; if the wireless device 100 is in MICO mode and theAMF 155 notifies or previously notified an SMF 160 of the wirelessdevice 100 being unreachable such that the SMF 160 may not send DL datanotifications to the AMF 155; and/or if the SMF 160 had subscribed forwireless device 100 reachability status such that the AMF 155 mayprovide a notification of the wireless device 100 reachability.

If a wireless device 100 triggered service request procedure (such asshown in FIGS. 8A, 8B, 13A, and 13B) may be in progress, a currentand/or new wireless device 100 triggered service request procedure maycause unnecessary data notification messages, which may increase a loadof the AMF 155. Data notifications (e.g., downlink data notifications)may occur if sending uplink data by the wireless device 100 may causearrival of data (e.g., downlink data) after or in response to the uplinkdata that may arrive at the UPF 110 (e.g., before arrival of an N4session modification request indicating that the data may be sent fromthe UPF 110 to the (R)AN 105 and the wireless device 100). The AMF 155may not send a paging message to the wireless device 100, for example,if the AMF 155 receives a data notification or a packet notificationfrom the SMF 160, for example, during the wireless device triggeredservice request procedure and/or before the establishment of thedownlink user plane (e.g., UP connectivity). The AMF 155 may monitor(e.g., across all of the wireless devices served by the AMF 155) a firstrate at which data notifications may arrive. If the first rate maybecome significant (e.g., as configured by an operator) and/or if theload at the AMF 155 exceeds a threshold or a configured value (e.g., anoperator configured value), the AMF 155 may request to delay sendingdata notifications (e.g., by sending a packet notification delayrequest, a delay downlink data notification message, a delay downlinkpacket notification message, and/or the like). The request may beprocessed at the SMF 160 and/or at the UPF 110. The AMF 155 mayindicate, to the SMF 160, a request to delay data notification based ona value and/or for a time duration of a first delay duration parameter(e.g., the value of the first delay duration parameter may be given asan integer multiple of 50 milliseconds such as 100 milliseconds, 150milliseconds, zero, or by any other value). The SMF 160 and/or the UPF110 may use the value of the first delay duration parameter to delay inbetween receiving (downlink) data and sending the (downlink) datanotification message. The AMF 155 may update the value of the firstdelay duration parameter (e.g., the first rate of data notificationarrivals may be monitored every 60 seconds or other duration and thevalue of the first delay duration parameter may be determined by the AMF155). The AMF 155 may use an N11 message (e.g.,Nsmf_PDUSession_UpdateSMContext Request message), and/or the like, ofthe wireless device 100 initiated service request procedure to indicatedelaying (downlink) data notification request to send the first delayduration parameter to the SMF 160.

To determine the amount of delay requested by a given AMF 155, the SMF160 may use the last N11 message (e.g., Nsmf_PDUSession_UpdateSMContextRequest message) which may be part of the service request procedure,and/or the SMF 160 may use one of the N11 messages (e.g.,Nsmf_PDUSession_UpdateSMContext Request messages) of a service requestreceived within the preceding t time units (e.g., t may be 30 seconds orany other value). The AMF 155 may determine the value for the firstdelay duration parameter, for example, by adaptively increasing thevalue if a rate of data notification arrival at the AMF 155 is high(e.g., above a threshold value) and/or decreasing the value if the rateof data notification arrival at the AMF 155 is low (e.g., below athreshold value). The AMF 155 may monitor and/or measure the averagetime from the reception of the unnecessary (downlink) data notificationto the reception of the N11 request message or an N11 response from theSMF 160 in the same wireless device 100 triggered service requestprocedure. The value of the first delay duration parameter may bedetermined from a measured average, for example, by adding a safetymargin.

The SMF 160 and/or the UPF 110 may (e.g., for wireless devices of theAMF 155) buffer the (downlink) data for a period that may be determinedby a timer based on the first delay duration parameter, for example, ifthe SMF 160 and/or the UPF 110 determines from the last N11 messageand/or N4 session modification request (which may be part of the servicerequest procedure) that the AMF 155 may request delaying of the(downlink) data notification by the value of the first delay durationparameter. If the DL-TEID and (R)AN 105 (e.g., a gNB) address for thewireless device 100 is received before the expiry of the timer, thetimer may be cancelled, and the network triggered service requestprocedure may be finished without sending the (downlink) datanotification message to the AMF 155 (e.g., (downlink) data may be sentto the wireless device 100). If the timer expires, the (downlink) datanotification message may be sent to the AMF 155 after or in response toexpiry of the timer.

A wireless device may request services associated with one or morenetwork slices. The wireless device may initiate a session requestprocedure to request such services. The one or more network slices maycomprise an isolated network slice in addition to a network slice thatmay not be an isolated network slice. A session request may comprise anetwork slice isolation information parameter. Based on the networkslice isolation information parameter, a UPF may be selected that mayprovide the requested services. An SMF may select the UPF, for example,based on a list of candidate UPFs. An SMF may send, to an NRF, adiscovery request comprising the network slice isolation informationparameter. One or more UPFs may register with the NRF. The NRF mayselect and identify a UPF for the SMF. The session request may be in afirst network slice and the selected UPF may be in a second networkslice. By including the network slice isolation information parameter inthe session request and using the parameter to select a UPF, resourcesmay be shared between network slices and isolation requirements may besatisfied and/or may not be violated.

An access and mobility management function (AMF) may send, to a sessionmanagement function (SMF), a first message indicating a request toestablish a packet data unit (PDU) session and comprising a networkslice isolation information parameter. The first message may furthercomprise an identifier of the PDU session, an identifier of a wirelessdevice associated with the PDU session, and/or a network sliceidentifier of the PDU session. The SMF may receive the first message.The SMF may determine whether a user plane function (UPF) may berequired for the PDU session. The SMF may send, to a network repositoryfunction (NRF) and based on a determination that a UPF is required forthe PDU session, a second message comprising: the network sliceisolation information parameter, and/or a network slice identifier ofthe PDU session. The NRF may receive the second message. The NRF mayselect, based on the network slice isolation information parameterand/or the network slice identifier of the PDU session, a UPF (e.g., aselected UPF and/or a first UPF). The NRF may receive, from one or moreUPFs (e.g., the selected UPF), a registration request message comprisinga single network slice selection assistance information (S-NSSAI)associated with the one or more UPFs, and/or an identifier of the one ormore UPFs. The NRF may receive, from the one or more UPFs (e.g., theselected UPF and/or the first UPF) a domain name of the one or moreUPFs, a data network name, and/or an address of the one or more UPFs.Additionally or alternatively, the SMF may send, to a unified datamanagement (UDM) or any other device, and based on a determination thata UPF is required for the PDU session, a message comprising the networkslice isolation information parameter and/or a network slice identifierof the PDU session. The NRF may send, to the UDM, a message comprisingthe network slice information and/or the network slice identifier of thePDU session. The NRF may receive, from the UDM and based on the messageto the UDM, a message comprising subscriber data (e.g., for the wirelessdevice associated with the PDU session). The NRF may send, to the SMFand based on the second message, a third message comprising anidentifier of the selected UPF. The SMF may receive the third message.The UDM or other device may send, to the SMF and based on the messagefrom the SMF, a message comprising subscriber data (e.g., for thewireless device associated with the PDU session) and/or the networkslice isolation parameter. The NRF, UDM, SMF, and/or another device mayselect a UPF for the PDU session. The SMF may select for the PDU sessiona UPF, for example, if the SMF does not receive a selected UPF from theNRF, UDM, and/or another device. The SMF may determine, based on thenetwork slice isolation parameter, a UPF selection rule. The UPFselection rule may comprise an isolation policy comprising at least oneof a logical full isolation of network slices, a physical full isolationof the network slices, and/or network functions that are allowed to beshared among the network slices. The UPF selection rule may be based ona network slice coexistence constraint. The SMF may select the UPF, forexample, based on the subscriber data, the UPF selection rule, and/or alist of one or more candidate UPFs (e.g., which may be stored at the SMFand/or received in one or more messages from the NRF, UDM, or anotherdevice). The selected UPF may be associated with the network sliceidentifier of the PDU session. The SMF may send, to the selected UPF, afourth message comprising a request to establish the PDU session. Thefourth message may comprise an N4 PDU session establishment request. TheUPF may send, to the SMF, a fifth message comprising a response to therequest to establish the PDU session. The SMF may receive the fifthmessage. The PDU session may be established with a wireless device suchthat the wireless device may use resources of an isolated network slice.The wireless device may send uplink data. The wireless device mayreceive downlink data. A computing device may comprise: one or moreprocessors, and memory storing instructions that, when executed, causethe computing device to perform one or more of the above steps. A systemmay comprise: a first computing device configured to perform one or moreof the above steps, a second computing device configured to send thefirst message, and/or one or more additional computing devicesconfigured to perform one or more of the above steps. Acomputer-readable medium may store instructions that, when executed,cause the performance of one or more of the above steps.

UPF selection procedures may be enhanced by considering the SMF, UPFconnectivity, and/or topology that may allow one UPF to be shared amongmore than one SMFs. UPF selection criteria may be enhanced by takinginto account the constraints pertaining to resource isolation, networkisolation, and/or network slice coexistence and isolation. UPF discoverymay be enhanced based on various aspects of resource isolationrequirements such as network slice isolation. Selection of a UPF thatviolates a rule of isolation and/or coexistence constraints may causeservice interruptions and excessive signaling.

UPF selection based on network slice isolation information parametersmay provide a variety of advantages. Examples such as security,emergency, differentiated service levels, and the like may be enhancedby UPF selection based on network slice isolation informationparameters. One or more users associated with a particular group (e.g.,security, emergency, corporation, law enforcement, etc.) may have afirst type of access within a first area (e.g., at an office, in asecure location, within a registered vehicle, etc.) and/or during afirst period of time (e.g., on duty, during regular working hours,etc.). The one or more users may have a second type of access within asecond area (e.g., unauthorized areas, public areas, etc.) or during asecond period of time (e.g., off duty, during evening and/or weekendhours, etc.). One or more first network slices may be restricted to thefirst area and/or the first period of time. One or more second networkslices may be restricted to the second area, allowed except in the firstarea, restricted to the second period of time, and/or allowed exceptduring the first period of time. The first type of access may be limitedto use by authorized persons, in an authorized location, and/or duringan authorized time. If a first user requests service of the first typeof access, by providing a network slice isolation information parameterthat may be associated with the first type of access, network resourcesmay be allocated to enable access by the first user. If a second userrequests service of the first type of access but does not provide anetwork slice isolation information parameter that may be associatedwith the first type of access, the second user may be restricted fromaccessing resources associated with the first type of access. The seconduser may be allocated resources that are associated with the second typeof access rather than the first type of access. Any number of types ofaccess (e.g., classes) may be used. Each type of access may beassociated with a particular S-NSSAI. Each type of access may beassociated a particular service. As another example, a third user (e.g.,security officer) that is within the first area (e.g., a securefacility) during the first period of time (e.g., on duty) may be able toaccess a first network slice for secure communications within the firstarea. If the third user exits the first area (e.g., outside of a securefacility) and/or requests services outside the first period of time(e.g., off duty), the third user may not be able to access the firstnetwork slice (e.g., may not be able to access secure communications)but may be able to access non-secure communications outside the firstarea and/or outside the first period of time. If network slice isolationinformation parameters are not used for a service request, a UPF may beselected that may violate a security requirement, privacy setting, orother rule, for example, such that a user may not be able to access anetwork slice for requested service and/or such that resources may beallocated in an inefficient manner. By using network slice isolationinformation parameters, network resources may be allocated such thatnetwork slices configured for certain types of services may be properlyallocated to those services to improve efficiency of resources, increasesecurity of certain communications, provide varied service levels,and/or the like. Isolation constraints may be based on internalregulation (e.g., of a subscriber, of an employer, of an operator,and/or the like). For an example, it might be forbidden for a wirelessdevice to access a regular service and a set of specific servicessimultaneously, such that a wireless device used by a government officeror other position or group might be restricted to be either in off-duty(e.g., regular) or on-duty (e.g., specific) mode. It may be forbidden(e.g., by regulation or rule) for the wireless device to accesssimultaneously the off-duty services and the on-duty services. Theisolation constraints may be based on one or more network capabilities.For an example, a factory device may have multiple modes of operations,such as maintenance mode (e.g., which may be used to perform updates,blueprints upload, check the status of devices, monitoring andmaintenance, and/or the like) and a lower latency factory mode in whichthe device may receive ultra-reliable low-latency communications (URLLC)related commands to perform a particular duty. One or more networkfunction instance used for the URLLC factory slice may be tailoredspecifically to a particular duty and/or may not be able to supportother services such as file database access, and/or the like. A wirelessdevice may be required to select a single mode, as opposed to aplurality of modes simultaneously, or a set or subset of a plurality ofmodes.

An isolated network slice, may be supported based on one or more of thefollowing considerations: isolation and/or coexistence requirements maybe set by the wireless device 100 and/or a network such as shown in FIG.1 (e.g., based on policy and/or subscription information);implementation of an isolated network slice based on the SMF 160 and/orUPF 110 topology that may consider a certain UPF that may be sharedamong more than one SMFs; and/or selection of a proper UPF 110 for anisolated network slice. Enhancements for network slices may provide:improved implementations of an isolated network slice; selection of aproper UPF 110 for different types (e.g., category, level) of anisolated network slice; and/or determination of the proper UPF 110 basedon one or more isolation and/or coexistence policies and/orrequirements.

The wireless device 100 may request fully isolated network slice(s)and/or partially isolated network slices, for example, if performing aservice request procedure, a PDU session establishment procedure, and/orthe like. For a PDU session establishment procedure, the wireless device100 may send, to the AMF 155, a NAS message (and/or an SM NAS message)comprising one or more of: a network isolation information parameter,NSSAI, S-NSSAI (e.g., requested S-NSSAI, allowed S-NSSAI, subscribedS-NSSAI, and/or the like), DNN, PDU session ID, request type, old PDUsession ID, N1 SM container (e.g., PDU session establishment request),and/or the like. The wireless device 100 may establish a new PDUsession, for example, by generating a new PDU session ID. If emergencyservice may be required and an emergency PDU session is not already beestablished, the wireless device 100 may initiate the wireless devicerequested PDU session establishment procedure with a request typeindicating an emergency request (e.g., Emergency Request). In anexample, the wireless device 100 may initiate the wireless devicerequested PDU session establishment procedure by sending the NAS messagecomprising a PDU session establishment request within an N1 SMcontainer. The PDU session establishment request may comprise, forexample, a PDU type, SSC mode, protocol configuration options, and/orthe like. A request type may indicate an initial request, for example,if the PDU session establishment is a request to establish the new PDUsession. A request type may indicate an existing PDU session, forexample, if the request refers to an existing PDU session between 3GPPaccess and non-3GPP access, and/or if the request refers to an existingPDN connection in EPC. The request type may indicate an emergencyrequest, for example, if the PDU session establishment is a request toestablish a PDU session for emergency services. The request type mayindicate an existing emergency PDU session, for example, if the requestrefers to an existing PDU session for emergency services between 3GPPaccess and non-3GPP access. The NAS message sent by the wireless devicemay be encapsulated by the AN in an N2 message towards the AMF that maycomprise user location information and/or access technology typeInformation. The PDU session establishment request message may comprisean SM PDU DN request container comprising information for the PDUsession authorization by an external DN. The wireless device may includethe old PDU session ID (which may indicate the PDU session ID of theon-going PDU session that is to be released) in the NAS message, forexample, if the procedure may be triggered for an SSC mode 3 operation.The old PDU session ID may be an optional parameter. The AMF 155 mayreceive, from the AN, the NAS message (e.g., NAS SM message) togetherwith user location information (e.g., cell identifier such as for the(R)AN 105). The wireless device may not trigger a PDU sessionestablishment for a PDU session corresponding to a LADN if the wirelessdevice is outside the area of availability of the LADN.

The AMF 155 may determine that the NAS message or the SM NAS message maycorrespond to the request for the new PDU session, for example, based ona request type indicating an initial request and/or a determination thatthe PDU session ID may not be used for any existing PDU session(s) ofthe wireless device 100. If the NAS message does not contain an S-NSSAI,the AMF 155 may determine a default S-NSSAI for the requested PDUsession. The AMF 155 may determine a default S-NSSAI based on thewireless device subscription (e.g., if it comprises a default S-NSSAI)and/or one or more operator policies. The AMF 155 may select an SMF 160.The AMF 155 may store an association of the S-NSSAI, the PDU session ID,and/or an SMF ID, for example, if the request type indicates an initialrequest and/or if the request may be due to a handover from an EPS. TheAMF 155 may select the SMF 160 and may store an association of the newPDU session ID and the selected SMF ID, for example, if the request typeis an initial request and/or if the old PDU session ID indicates theexisting PDU session may be contained in the message (e.g., NASmessage).

FIG. 14 and FIG. 15 show example methods for establishing an isolatednetwork slice. At step 1401 and at step 1501, the AMF 155 may send, tothe SMF 160, a message such as an N11 message (e.g.,Nsmf_PDUSession_CreateSMContext Request, Nsmf_PDUSession_UpdateSMContextRequest, and/or PDU session establishment and/or modification request).The message may indicate a session creation and/or modification message.The message may comprise a network isolation information parameter, atype name of a network function, and/or the like. An N11 message such asan Nsmf_PDUSession_CreateSMContext Request message may comprise one ormore of: a SUPI and/or PEI, a DNN, an S-NSSAI, a PDU session ID, an AMFID, a request type, an N1 SM container (e.g., a PDU sessionestablishment request), user location information, an access type, aPEI, a GPSI). An N11 message such as an Nsmf_PDUSession_UpdateSMContextRequest may comprise one or more of: a SUPI, a DNN, an S-NSSAI, a PDUsession ID, an AMF ID, a request type, and/or an N1 SM container (e.g.,a PDU session establishment request and/or a PDU session modificationrequest), user location information, access type, RAT type, and/or PEI).The AMF 155 may invoke the Nsmf_PDUSession_CreateSMContext Request, forexample, if the AMF 155 may not have an association with the SMF 160 forthe PDU session ID provided by the wireless device 100 (e.g., if requesttype indicates an initial request). The AMF 155 may invoke theNsmf_PDUSession_UpdateSMContext Request, for example, if the AMF 155already has an association with an SMF for the PDU session ID providedby the wireless device 100 (e.g., if request type indicates an existingPDU session). The AMF 155 ID may be the wireless device's 100 GUAMIwhich may uniquely identify the AMF 155 serving the wireless device 100.The AMF 155 may forward the PDU session ID together with the N1 SMcontainer comprising the PDU session establishment request received fromthe wireless device 100. The AMF 155 may provide the PEI instead of theSUPI, for example, if the wireless device has registered for emergencyservices without providing the SUPI. The AMF 155 may indicate that theSUPI has not been authenticated, for example, if the wireless device 100has registered for emergency services but has not been authenticated.

The SMF 160 may register with the UDM 140, for example, if the requesttype indicates neither an emergency request nor an existing emergencyPDU session, and if the SMF 160 has not yet registered and subscriptiondata may not be available. The SMF 160 may retrieve, from the UDM 140,subscription data and/or subscribers to be notified when subscriptiondata may be modified. The SMF 160 may determine that the request may bedue to a handover between 3GPP access and non-3GPP access and/or due toa handover from EPS, for example, if the request type may indicate anexisting PDU session or an existing emergency PDU session. The SMF 160may identify the existing PDU session based on the PDU session ID. TheSMF 160 may not create a new SM context. The SMF 160 may update theexisting SM context. The SMF 160 may provide the representation of theupdated SM context to the AMF 155, for example, in a response to therequest. The SMF 160 may determine and/or identify an existing PDUsession to be released based on an old PDU session ID, for example, ifthe request type indicates an initial request and/or if the old PDUsession ID is to be included in the request (e.g.,Nsmf_PDUSession_CreateSMContext Request).

At step 1408 and at step 1506, the SMF 160 may send, to the AMF 155, anN11 message response (e.g., Nsmf_PDUSession_CreateSMContext Response,Nsmf_PDUSession_UpdateSMContext Response, and/or PDU sessionestablishment and/or modification response). An N11 message such as anNsmf_PDUSession_CreateSMContext Response may comprise one or more of: anindication of a cause, an SM context ID, and/or an N1 SM container(e.g., a PDU session reject (which may comprise an indication of acause).

The SMF 160 may select a UPF 110 and/or trigger a PDU sessionestablishment authentication and/or authorization, for example, if theSMF 160 is required to perform secondary authorization and/orauthentication during the establishment of the PDU session by a DN-AAAserver. The SMF 160 may select an SSC mode for the PDU session, forexample, if the request type indicates an initial request. The SMF 160may select one or more UPFs as needed. The SMF 160 may allocate an IPaddress and/or prefix for the PDU session, for example, if the PDU typeis IPv4 and/or IPv6. The SMF 160 may allocate an interface identifier tothe wireless device 100 for the wireless device 100 to build itslink-local address, for example if the PDU type is IPv6. The SMF 160 mayallocate an IPv6 prefix for the PDU session and an N6 point-to-pointtunneling (based on UDP/IPv6), for example, if the PDU type is anunstructured PDU type.

Selection of the UPF 110 may be performed locally by the SMF (such asshown in FIG. 15), or assisted by the NRF 130 (such as shown in FIG.14). The selection of a proper UPF 110 may require consideration ofisolation and/or coexistence requirements requested by the wirelessdevice 100 and/or determined by a network such as shown in FIG. 1 (e.g.,determined by the AMF 155 based on one or more of subscriptioninformation, an operator policy, and/or the like).

The isolation may comprise one or more of a topological isolation (e.g.,logical, or physical), a functional isolation, a physical resourceisolation, and/or a transactional isolation. A degree of isolation maybe determined based on one or more of a logical and/or physical fullisolation and/or a partial isolation, and/or a number and/or a type ofnetwork functions that may be allowed to be shared among network slices.The degree of isolation may be part of a selection rule for selectingthe proper UPF 110.

At step 1401 in FIG. 14, the SMF 160 may receive, from the AMF 155, themessage (e.g., N11 message) such as described above. The message maycomprise an indication indicating a first session creation request (or asession modification request) message for the wireless device 100. Afteror in response to receiving the first session creation request (or thesession modification request) message by the SMF 160, from the AMF 155,the SMF 160 may send, at step 1402, to the NRF 130, a first messageindicating that discovery of a network function may be required. Thenetwork function may be a user plane network function (e.g., the UPF110, a user plane function for CIoT, a user plane function for vehicularapplications, NB-IoT, and/or the like), the UPF 110, and/or the like.The first message may comprise the network isolation informationparameter, a type name of the network function, a name (e.g.,identifier) of the network function, a name (e.g., identifier) of theSMF 160, at least one S-NSSAI associated with at least one networkslice, a user identity associated with the wireless device 100, anidentifier associated with the wireless device 100, at least one DNN, aPLMN identifier (of the network function), and/or the like. The firstmessage may comprise an Nnrf_NFDiscovery_Request message. TheNnrf_NFDiscovery_Request message may be part of an NRF service discoveryservice such as an Nnrf_NFDiscovery service. The NRF service discoveryservice may enable the SMF 160 to discover a set of network functions,NF instances (e.g., with specific NF service), or a target NF type(e.g., the user plane function, the UPF 110, and/or the like), and/orenable the SMF 160 to discover a specific NF service. TheNnrf_NFDiscovery_Request message may comprise a target NF service name,NF type of the target NF, NF type of the NF service user (e.g., the SMF160), and/or the like.

The NRF 130 may select a user plane function (e.g., the UPF 110) basedon one or more elements of the first message and/or a network isolationinformation parameter. The network isolation information parameter maybe used to determine a selection rule for the user plane function (e.g.,the UPF 110). The selection rule may comprise the degree of isolation,type of isolation, and/or the like.

The NRF 130 may query the UDM 140 for a selection of the UPF. At step1403, the NRF 130 may send, to the UDM 140, a subscriber data requestmessage. The UDM 140 may determine information for a selection of theUPF. At step 1404, the UDM 140 may send, to the NRF 130, a subscriberdata response message. The subscriber data response message may comprisean indication for the selection of the UPF, an identifier of the UPF,subscriber policy information to determine a selection rule that may bebased on, for example, location, existing PDU sessions of the wirelessdevice 100, network slices associated with the wireless device 100,and/or the like. The UDM 140 may support storing data in a unified datalayer that may comprise user subscription data, policy data (e.g., perwireless device related policy data, and/or per application relatedpolicy data), network data (e.g., wireless device traffic reports fromUP NFs, and/or the NF topology information in user plane for UP NFdiscovery and selection), service information (e.g., the user locationinformation and/or UP anchor information used for handover betweendifferent access networks), and/or the like. The NF topology informationmay comprise network nodes hosting UP NFs (e.g., the UPF 110), and/orlogical links connecting network nodes. Attributes of network nodes maycomprise resources reserved for UP NFs, such as input and output ports,and/or processing capabilities (e.g., throughput and/or number ofsupported wireless devices and/or PDU sessions). Attributes of logicallinks may comprise, for example, link capacity limit(s). The UPF 110topology may comprise attributes of logical links connecting networknodes such as link capacity limit, attributes of connected network nodessuch as input and/or output ports and processing capabilities, and/orthe like. UPF 110 topology may be used for UPF 110 selection and/orreselection based on constraints of the network isolation informationparameter. The constraints may be associated with a subscription basedpolicy, a topological isolation (logical, or physical) constraint, afunctional isolation, a physical resource isolation, a transactionalisolation constraint, and/or the like. A degree of isolation may bedetermined based on one or more of a logical and/or physical fullisolation and/or partial isolation, and/or a number and/or type ofnetwork functions that may be allowed to be shared among network slices.

At step 1405, the SMF 160 may receive, from the NRF 130, a secondmessage. The second message may comprise a network function identifierand/or an IP address of the UPF 110, and/or the like. The networkfunction identifier may be a fully qualified domain name (FQDN) of theuser plane function (e.g., the UPF 110). The second message may comprisean Nnrf_NFDiscovery_Response message. The Nnrf_NFDiscovery_Responsemessage may comprise part of a NRF service discovery service (e.g., anNnrf_NFDiscovery service). The NRF service discovery service may enablethe SMF 160 to discover a set of network functions, NF instances withspecific NF service, and/or a target NF type (e.g., the user planefunction, the UPF 110, and/or the like), and/or may enable the SMF 160to discover a specific NF service. The Nnrf_NFDiscovery_Response messagemay comprise FQDN and/or IP address(es) for the target service name(e.g., the UPF 110). FQDN and IP addresses may belong to a set ofrequested target NF instance(s), or NF service instance(s).

UPF 110 selection by the SMF 160 may utilize the NRF 130 to discover theUPF instance(s). The SMF 160 may send a discovery request (e.g., at step1402) that may include the network isolation information parameter, DNN,S-NSSAI, DNAI, connectivity requirements (e.g., N3 and/or intra or interPLMN N9 and/or N6). After or in response to receiving the discoveryrequest, the NRF 130 may respond to the SMF 160 with the IP addressand/or the FQDN of corresponding UPF 110 instance(s) (e.g., at step1405). The NRF 130 may provide the SMF 160 with information to assistUPF 110 selection (e.g., including UPF 110 location, UPF 110 capacity,and UPF 110 optional functionalities and capabilities, and/or the like).The SMF 160 may select the UPF 110 based on the network isolationinformation parameter. The SMF 160 may determine a network functionidentifier and/or the IP address(es) of the UPF 110.

At step 1406, after or in response to receiving the second messageand/or selecting/determining the UPF 110 by the SMF 160, the SMF 160 maysend, to the UPF 110 as the selected user plane network function, asession establishment and/or modification message (e.g., an N4 sessionestablishment and/or modification). The SMF 160 may send an N4 sessionestablishment and/or modification request based on a network functionidentifier and/or IP address(es) of the UPF 110. The network isolationinformation parameter may be a factor used to determine a selection rulebased on a degree of isolation. The session establishment and/ormodification may be part of N4 session management procedures that may beused to control the functionality of the UPF 110. The SMF 160 maycreate, update, and/or remove an N4 session context in the UPF 110. TheN4 session establishment procedure may be used to create the initial N4session context for a PDU session at the UPF 110. The SMF 160 may assigna new N4 session ID and may provide the new N4 session ID to the UPF110. The N4 session ID may be stored by both entities and/or may be usedto identify the N4 session context during their interaction. The SMF 160may store the relation between the N4 session ID and PDU session for thewireless device 100.

The N4 session modification procedure may be used to update the N4session context of an existing PDU session at the UPF 110, which may beexecuted between the SMF 160 and the UPF 110 if PDU session relatedparameters are modified. As part of the service request procedure and/orPDU session establishment, if the SMF 160 selects the UPF 110 (e.g., toact as intermediate UPF) for the PDU session, and/or if the SMF 160determines to insert an intermediate UPF 110 for a PDU session which didnot have an intermediate UPF, the N4 session establishment requestmessage may be sent to the UPF 110 (e.g., at step 1406). The N4 sessionestablishment request may comprise one or more of: packet detection,data forwarding, and/or enforcement and/or reporting rules for the UPF110.

At step 1407, the UPF 110 may send, to the SMF 160, a response message(e.g., an N4 session establishment response message). If UPF 110allocates CN tunnel information, the UPF 110 may provide DL CN tunnelinformation for the UPF 110 that may operate as a PDU session anchor andUL CN tunnel information (e.g., CN N3 tunnel information) to the SMF160. At step 1408, the SMF 160 may send, to the AMF 155, an N11 messageresponse such as described above.

The network slice isolation information parameter may be used toevaluate UPF 110 candidates, for example, based on the at least oneS-NSSAI of at least one network slice. The network slice isolationinformation parameter may comprise one or more constraints for S-NSSAIs.The one or more constraints for S-NSSAIs may be associated with one ormore classes of S-NSSAIs (e.g., mutual exclusion class information).Each S-NSSAI may be associated with a class. The S-NSSAI of the at leastone S-NSSAI may be one of the requested S-NSSAI, the subscriptionS-NSSAI, and/or allowed S-NSSAI. An allowed NSSAI may comprise one ormore S-NSSAIs corresponding to one or more network slices and/or networkslice instances to which the wireless device 100 may be allowed toaccess. The requested NSSAI may comprise one or more S-NSSAIscorresponding to one or more network slices or network slice instancesto which the wireless device 100 may register. The S-NSSAI may be one ofthe allowed S-NSSAIs. The wireless device 100 may comprise network sliceisolation information applied to the S-NSSAI. Subscribed NSSAI and/orsubscribed NSSAI related network slice instance(s) may comprise one ormore S-NSSAIs corresponding to one or more network slices and/or networkslice instances to which the wireless device 100 may be subscribed.Subscribed network slice isolation information may comprise one or morenetwork slice isolation type and/or level applied to the subscribedNSSAI and/or the subscribed NSSAI related network slice instance(s).

FIG. 15 shows an example method in which the SMF 160 may interact withthe UDM 140 for selection of the UPF 110. The selection and/orreselection of the UPF 110 may be performed by the UDM 140. The UDM 140may consider UPF 110 deployment scenarios such as slice isolationconstraints, slice coexistence constraints, logical topology, physicaltopology, UPF location (e.g., centrally located UPF 110 and distributedUPF 110 located close to or at the access network site), and/or thelike. At step 1501, the SMF may receive, from the AMF 155 the N11message such as described above. The N11 message may comprise anindication indicating a first session creation request (or the sessionmodification request) message for the wireless device 100.

At step 1502, after or in response to receiving the first sessioncreation request (or the session modification request) message by theSMF 160, from the AMF 155, the SMF 160 may send, to the UDM 140, adiscovery request and/or a subscriber data request. The request maycomprise an indication indicating that discovery of a network functionmay be required. The network function may be a user plane networkfunction (e.g., the UPF, a user plane function for CIoT, a user planefunction for vehicular applications, NB-IoT, and/or the like), the UPF110, and/or the like. The discovery request and/or subscriber datarequest may comprise the network isolation information parameter, thetype name of the network function, the name (e.g., identifier) of thenetwork function, at least one S-NSSAI associated with of at least onenetwork slice, the user identity associated with the wireless device100, an identifier associated with the wireless device 100, at least oneDNN, the PLMN identifier (e.g., of the network function), and/or thelike. The UDM 140 may select a user plane function (e.g., the UPF 110)based on the network isolation information parameter, the selectionrule, and/or the like.

At step 1503, the UDM 140 may send, to the SMF 160, a subscriber dataresponse message. The subscriber data response message may comprise anindication for the selection of the UPF (e.g., based on one or morenetwork isolation information parameters, slice isolation parameters,and/or the like). The network isolation information parameter, theselection rule, and/or the like may be provided by the UDM 140 (e.g., atstep 1503 such as in the subscriber data response message). The SMF 160may locally select the UPF 110 based on the network isolationinformation parameter and/or the selection rule received from the UDM140. The UDM 140 may notify the SMF 160 if the selection rule (or thenetwork isolation information parameter) may change (e.g., uponinstantiation of a new UPF 110, isolation policy change, and/or thelike).

The SMF 160 may determine the UPF 110, for example, based on the priorinformation received from the NRF 130, the UDM 140, and or the like. TheSMF 160 may determine the UPF 110 based on information in the N11message (e.g., received at step 1501). The SMF 160 may determine the UPF110 based on information received in the subscriber data responsemessage (e.g., received at step 1503). The SMF 160 may select the UPF110 based on local information at the SMF 160. The selection and/orreselection of UPF 110 may require the network isolation informationparameter, topology information of one or more (e.g., all) of the UPFscontrolled by the SMF 160 that may be known by the SMF 160 if the UPF110 is available and/or instantiated. UPF topology may be used by theSMF 160 to determine whether the isolation requirements provided and/orderived based on the network isolation information parameter may be metif the UPF 110 is selected. The SMF 160 may evaluate any availableinformation on logical topology, physical topology (e.g., a graph of theUPF/SMF connectivity), and/or the like to evaluate the suitability ofeach candidate UPF, for example, if selection/reselection of the UPF 110is triggered. UPF topology may have multiple parameters such as addedlatency on the links (e.g., N3, N9, and/or N6), added jitter on thelinks, link capacity and remaining capacity, actual monetary costs(e.g., if resources are rented from a third party), UPF capacity and/oravailability, the DNAI(s) to be used in priority (e.g., if severalchoices are available). UPF 110 selection and/or reselection may occurregularly and/or frequently (e.g., on a periodic or aperiodic basis) bythe SMF 160, for example, to determine whether a relocation and/orreallocation of the UPF 110 may be required. The UPF 110 may update theSMF 160, for example, if there may be any change in topology parameters(e.g., logical or physical topology, and/or the like). The SMF 160 mayevaluate the UPF 110 to ensure that the isolation requirements aresatisfied.

At step 1504, after the SMF 160 selects and/or determines the UPF 110,the SMF 160 may send, to the selected user plane network function (e.g.,UPF 110) a second session creation message. The second session creationmessage may comprise, for example, a session establishment and/ormodification message, an N4 session establishment and/or modification,and/or the like. The second session creation message (e.g., the sessionestablishment and/or modification) may be part of the N4 sessionmanagement procedures that may be used to control the functionality ofthe UPF 110. The SMF 160 may create, update, and/or remove the N4session context in the UPF 110. The N4 session establishment proceduremay be used to create the initial N4 session context for the PDU sessionat the UPF 110. The SMF 160 may assign a new N4 session ID. The SMF 160may provide the new N4 session ID to the UPF 110. The N4 session ID maybe stored by the SMF 160 and/or the UPF 110. The N4 session ID may beused to identify the N4 session context during an interaction betweenthe SMF 160 and the UPF 110. The SMF 160 may store the relation betweenthe N4 session ID and the PDU session for the wireless device 100.

The N4 session modification procedure may be used to update the N4session context of an existing PDU session at the UPF 110. The N4session modification procedure may be performed (and/or re-performed)between the SMF 160 and the UPF 110 if the PDU session relatedparameters are modified. The N4 session establishment request messagemay be sent to the UPF 110 as part of the service request procedure orPDU session establishment, for example, if the SMF 160 selects the UPF110 (e.g., to act as intermediate UPF) for the PDU session and/or if theSMF 160 determines to insert an intermediate UPF for a PDU session thatdid not have an intermediate UPF. The N4 session establishment requestmay comprise packet detection, data forwarding, and/or enforcementand/or reporting rules for the UPF 110.

At step 1505, the UPF 110 may send, to the SMF 160, a response message(e.g., an N4 session establishment and/or modification response). TheUPF 110 may provide, to the SMF 160, DL CN tunnel information for theUPF 110 that may operate as a PDU session anchor and UL CN tunnelinformation (e.g., CN N3 tunnel information), for example, if the UPF110 allocates CN tunnel Information. At step 1506, the SMF 160 may send,to the AMF 155, an N11 message response such as described above.

The network isolation information parameter, the selection rule, and/orthe like may be provided by the NRF 130. The SMF 160 may locally selectthe UPF 110 based on the network isolation information parameter and/orthe selection rule. The NRF 130 may receive the network isolationinformation parameter from the UDM 140. The NRF 140 may notify the SMF160 if the selection rule changes or may change (e.g., uponinstantiation of a new UPF 110, isolation policy change, and/or thelike). If the new UPF 110 (instance) is instantiated, the new UPF 110,may send a notification to the NRF(s) or the SMF(s) that it may access(e.g., those permitted within the same PLMN and/or the like). The NRF130 may notify the SMF 160 of any change in the status of the UPF 110(e.g., topology changes).

The UPF 110 (e.g., a new UPF instance) may configure itself to the NRF130. The UPF 110 may issue a registration management request operation(e.g., an Nnrf_NFManagement_NFRegister Request operation) to the NRF 130(that may be provided by the OAM). The registration management requestoperation may provide the UPF 110's NF type, the FQDN of the UPF 110,endpoint addresses, the IP address(es) to be used for N4 interactions,the list of S-NSSAI and/or DNN that the UPF 110 may support, and/or thelike. The NRF 130 may determine the proper UPF 110 candidate base on theinformation received via the Nnrf_NFManagement_NFRegister Request. TheNRF 130 may evaluate the information based on the network isolationinformation parameter.

The network isolation information parameter may comprise a vector ofelements with dimension k, wherein k may be an integer. The elements ofthe vector may be indicators for the degree of isolation, the selectionrule, an isolation constraint type, a utility function for amulti-attribute selection function, isolation constraints, coexistenceconstraints, and/or the like. The network isolation informationparameter may comprise one or more indication parameters indicating atleast one of the degree of isolation, the selection rule, an isolationconstraint type, a utility function for a multi-attribute selectionfunction, isolation constraints, coexistence constraints, and/or thelike.

The degree of isolation may be the number of network functions that areallowed to be shared among two or more network slices (or network sliceinstances). As an example, a degree of isolation being 1 may suggestthat one network function may be shared among two or more network slices(or network slice instances).

The wireless device 100 may include the network isolation informationparameter during the registration request procedure. The networkisolation information parameter may comprise one or more of networkslice isolation type and/or level for each of the requested S-NSSAIs fornetwork slices and/or network slice instances. Slice isolation types andlevels may be associated with a fully isolated network slice, a partlyisolated network slice with a shared (R)AN, a partly isolated networkslice with a shared (R)AN and a shared AMF, and/or the like. The networkisolation information parameter may be included in the S-NSSAI with anadded (e.g., optional) element indicating the slice (or slice instance)isolation type (e.g., a 2-bit element, or any other size element,wherein the combination may comprise any number of combinations of fullyisolated network slice, partly isolated network slice with shared (R)AN,partly isolated network slice with shared (R)AN and shared AMF, and/orthe like). A separate information element may be used that may comprise,for example, the isolation type wherein the combination may comprise anynumber of combinations of fully isolated network slice, partly isolatednetwork slice with shared (R)AN, partly isolated network slice withshared (R)AN and shared AMF, and/or the like.

FIG. 16 shows an example of a partially isolated network slice with ashared (R)AN 105. The shared (R)AN 105 may be shared between two CNnetwork slices or slice instances 1601 and 1602. The first CN sliceinstance 1601 may comprise a first SMF 160-1 and a first UPF 110-1. Thesecond CN slice instance 1602 may comprise a second SMF 160-2 and asecond UPF 110-2. Each of the first CN slice instance 1601 and thesecond CN slice instance 1602 may communicate with the shared (R)AN 105via a control plane (CP) and a user plane (UP).

FIG. 17 shows an example of a partially isolated network slice with ashared (R)AN 105 and a shared SMF 160. The first CN slice instance 1701may comprise a first UPF 110-1. The second CN slice instance 1702 maycomprise a second UPF 110-2. Each of the first CN slice instance 1701and the second CN slice instance 1702 may communicate with the shared(R)AN 105 via a user plane (UP). Each of the first CN slice instance1701 and the second CN slice instance 1702 may communicate with theshared SMF 160 via a control plane (CP). The SMF 160 may communicatewith the share (R)AN 105 via the control plane.

FIG. 18 shows an example of a first UP instance 1803 comprising the UPF110 controlled by two SMFs (e.g., SMF 160-1 associated with a first CNslice instance 1801, and SMF 60-2 associated with a second CN sliceinstance 1802) that may belong to two CN slices.

FIG. 19 shows an example of two fully isolated network slices such thatthe two network slices (or network slice instances) may share neitherthe core network functions nor the user plane functions with any othernetwork slice or network slice instance. A first network slice instance1901 may comprise one or more slice specific core network functions(e.g., slice CP NF 1 to slice CP NF N, and/or slice NP NF to slice NP NFx). The first network slice instance 1901 may be controlled by a firstRAN 105 a in communication with a first wireless device 100-1. A secondnetwork slice instance 1902 may comprise one or more slice specific corenetwork functions (e.g., slice CP NF 1 to slice CP NF N, and/or slice NPNF to slice NP NF x). The second network slice instance 1902 may becontrolled by a second RAN 105 b in communication with a second wirelessdevice 100-2. The first network slice instance 1901 and the secondnetwork slice instance 1902 may be two fully isolated network slices,wherein no network functions may be shared by the first network sliceinstance 1901 and the second network slice instance 1902.

FIG. 20 shows an example of a partially isolated network slice sharingthe (R)AN 105. The (R)AN 105 may be visible from outside the networkslice instances (e.g., from the PLMN level NRF 130). The (R)AN 105 maybe in communication with the first wireless device 100-1 and the secondwireless device 100-2. A first network slice instance 2001 and a secondnetwork slice instance 2002 may be two partly isolated network sliceswherein the (R)AN 105 may be shared by the first network slice instance2001 and the second network slice instance 2002. The first network sliceinstance 2001 and the second network slice instance 2002 may eachcomprise slice specific core network functions such as described aboveregarding the first network slice instance 1901 and the second networkslice instance 1902 shown in FIG. 19.

FIG. 21 shows an example of a partial isolation of two network sliceswith a shared (R)AN 105 and a shared AMF 155. Both the (R)AN 105 and theAMF 155 may be visible from outside the network slice instance(s). The(R)AN 105 may be in communication with the first wireless device 100-1and the second wireless device 100-2. A first network slice instance2101 and a second network slice instance 2102 may be two partly isolatednetwork slices wherein the (R)AN 105 and the AMF 155 may both be sharedby the first network slice instance 2101 and the second network sliceinstance 2102. The first network slice instance 2101 and the secondnetwork slice instance 2102 may each comprise slice specific corenetwork functions such as described above regarding the first networkslice instance 1901 and the second network slice instance 1902 shown inFIG. 19.

FIG. 22 shows an example method for providing an isolated network slice.A wireless device 100 may request services associated with one or morenetwork slices. The wireless device 100 may initiate a PDU sessionestablishment procedure, a service request procedure, and/or the like,to request such services. The one or more network slices may comprise anisolated network slice, which may be in addition to a network slice thatmay not be an isolated network slice. The wireless device may send, tothe (R)AN 105, one or more messages as part of a PDU sessionestablishment procedure, a service request procedure, and/or the like.The (R)AN 105 may send, to the AMF 155, one or more messages as part ofthe PDU session establishment procedure, the service request procedure,and/or the like. The AMF 155 may be in a first network slice 2201. TheAMF 155 may send, to the SMF 160, one or more messages as part of thePDU session establishment procedure, the service request procedure,and/or the like, in the first network slice 2201. The SMF 160 mayreceive, from the AMF 155, an N11 message (e.g., the N11 message fromthe AMF 155 to the SMF 160 as part of the PDU session establishmentprocedure, the N11 message from the AMF 155 to the SMF 160 as part ofthe service request procedure, and/or the like) indicating a firstsession creation request (or a session modification request message).The first session creation request may be part of the service requestprocedure, the PDU session establishment, and/or the like of thewireless device 100. The AMF 155 and the SMF 160 may perform a sessionrequest procedure such as described above regarding FIG. 14 and/or FIG.15. The session request procedure may be to establish a first PDUsession for a first network slice 2201.

The SMF 160 may determine, for example, after receiving a sessionrequest from the AMF 155, that a UPF is required to provide one or moreservices associated with the request from the wireless device 100. Thesession request may comprise a network slice isolation informationparameter. The SMF 160 may apply one or more isolation rules todetermine, based on the network slice isolation information parameter, aUPF that may provide the one or more requested services. For example,the SMF 160 may determine UPF 110 in a second network slice 2202 mayprovide the one or more requested services. The SMF 160 may send adiscovery message to the NRF 130, for example, prior to determining theUPF 110. The discovery message may comprise the network slice isolationinformation parameter. The NRF 130 may send a response to the SMF 160comprising an identifier of a selected UPF and/or a list of UPFs fromwhich the SMF 160 may select. The NRF 130 may obtain, from a UDM 140,information associated with one or more UPFs which the NRF 130 may useto select a UPF and/or provide a list of UPFs to the SMF 160. One ormore UPFs may register with the NRF 130. The NRF 130 may select a UPFfrom the one or more UPFs that may have registered with the NRF 130. TheSMF 160 may perform a connection setup procedure with a selected UPF(e.g., UPF 110) that may be in the second network slice 2202. A selectedUPF may comprise a plurality of UPFs, for example, one or moreintermediate UPFs (e.g., cascaded and/or in different topologies) thatmay comprise one or more uplink classifiers to divert traffic todifferent data networks. The one or more UPFs may comprise CP NF 192-2,CP NF 192-3, and/or UP NF 194-2.

The first session creation and/or modification request may comprise oneor more of the network isolation information parameter, NSSAI, S-NSSAI(e.g., requested S-NSSAI, allowed S-NSSAI, subscribed S-NSSAI, and/orthe like), DNN, PDU session ID, request type, old PDU session ID, N1 SMcontainer (e.g., PDU session establishment request), and/or the like. Ifthe SMF 160 determines that a new UPF (e.g., the UPF 110) may beselected (e.g., based on an initial request indication, an indicationfor selecting a new intermediate UPF 110, and/or the like), the SMF 160may select the new UPF (e.g., the UPF 110) based on one or more of thefollowing: the network isolation information parameter, dynamic load ofone or more UPFs, UPF's relative static capacity among UPFs supportingthe same DNN, UPF 110 location available at the SMF 160, wireless device100 location information, capability of the UPF 110, and/or thefunctionality required for the particular wireless device 100 session.An appropriate UPF 110 may be selected by matching the functionality andfeatures required for the wireless device 100, data network name (DNN),PDU session type (e.g., IPv4, IPv6, Ethernet type or unstructured type)and, if applicable, the static IP address and/or prefix, SSC modeselected for the PDU session, wireless device 100 subscription profilein UDM 140, DNAI as included in one or more PCC rules, one or more localoperator policies, S-NSSAI, access technology being used by the wirelessdevice 100, UPF logical topology, and/or the like. The SMF 160 mayperform a discovery procedure with the NRF 130, such as described aboveregarding FIG. 14. The SMF 160 may perform subscriber datarequest/response procedure with the UDM 140, such as described aboveregarding FIG. 15. The SMF may perform a connection setup procedure withthe selected UPF (e.g., UPF 110), such as described above regarding FIG.14 and FIG. 15. The discovery procedure and/or the connection setupprocedure may be to determine and setup a connection with a UPF for anisolated network slice 2202 that may be associated with the data network115.

FIG. 23 shows an example for UPF selection based on an isolationconstraint. The network isolation information parameter may be used toevaluate alternatives from a set of available UPFs, such as UPF 1, UPF2, UPF 3, UPF 4, or UPF X. The UPF selection procedure may be performedlocally at the SMF 160, by the NRF 130, by the UDM 140, or by anycombination of devices. A set of elements associated with each UPF(e.g., an affinity group) may be evaluated. UPF 1 may be associated witha set {SMF 1, SMF 3}. UPF_2 may be associated with a set {SMF 2}. UPF 3may be associated with a set {SMF3}. UPF 4 may be associated with a set{SMF4}. UPF 1, and SMF 1 belong to Slice 1. UPF 2, and SMF 2 belong toSlice 2. UPF 3, and SMF 3 belong to Slice 3. UPF 4, and SMF 4 belong toSlice 4. An isolation constraint may require that Slice 4 and Slice 1may not coexist. Slice 4 may initially have one UPF (e.g., UPF 4) andmay require a new UPF (e.g., UPF X). In order to select a new UPF (inaddition to UPF 4) for SMF 4 that belongs to Slice 4, the only candidatemay be UPF 2 among the set of {UPF 1, UPF 2, UPF 3}. As shown above, UPF1 may not be a suitable candidate because Slice 1 and Slice 4 may notcoexist. UPF 3 belongs to Slice 3 that is not be isolated from Slice 1,therefore, UPF 3 may not be a suitable candidate.

The degree of isolation may indicate a level of isolation. As anexample, a level of isolation greater than 1 may indicate that, althoughUPF 3 is not isolated from Slice 1, UPF 3 may be a suitable candidatebecause it may yield the coexistence of Slice 1 and Slice 4 as implicitor indirect (e.g., coexistence via Slice 3).

FIG. 24 shows an example method that may be performed by an SMF, such asthe SMF 160, to provide an isolated network slice. At step 2401, the SMF160 may receive a session creation and/or modification requestcomprising a network slice isolation parameter. The request may bereceived from the AMF 155. The request may comprise an N11 messageindicating a first session creation and/or modification request, such asdescribed regarding step 1401 of FIG. 14 and/or step 1501 of FIG. 15. Atstep 2402, the SMF 160 may determine to select a UPF based on one ormore isolation information constraints and/or the network sliceisolation parameter. UPF selection may be performed, for example, toaccommodate one or more isolated network slices for the wireless device100. The request may comprise a PDU session request. The PDU session maycomprise a network slice identifier. The network slice identifier maycomprise an information element comprising the network slice isolationinformation parameter. The network slice information parameter maycomprise a tuple of at least one information element, wherein the atleast one information element may comprise an isolation type descriptor,a degree of isolation, a selection rule, and/or an isolation constrainttype. At step 2403 the SMF 160 may determine whether a UPF is availablefrom a list of candidates at the SMF. Additionally or alternatively, oneor more UPF candidates may be identified by another device, such as theNRF 130 and/or the UDM 140. If a UPF is available from a list ofcandidates, the method may continue to step 2404. If a UPF is notavailable from the list of candidates, the method may continue to step2405.

At step 2404, the SMF 160 may select a UPF from a list of candidateUPFs. The UPF selection may be based on one or more isolationinformation constraints and/or the network slice isolation parameter.After step 2404, the SMF 160 may send, at step 2409, a sessionestablishment request to the discovered UPF, such as described regardingstep 1408 of FIG. 14 and step 1506 of FIG. 15.

At step 2405, the SMF 160 may determine whether to involve an NRF, suchas the NRF 130. If the SMF 160 determines to involve the NRF 130, forexample, to obtain information associated with one or more UPFcandidates, the method may continue to step 2406. If the SMF 160 doesnot determine to involve the NRF 130, the method may continue to step2407.

At step 2406, the SMF 160 may send, to the NRF 130, a discovery requestmessage comprising the network slice isolation parameter. Step 2406 maycorrespond to step 1402 described above regarding FIG. 14. The SMF 160may send the discovery request message after or in response to receivingan N11 message. The discovery request message may comprise a firstmessage indicating that discovery of a network function may be required.The first message may comprise the network slice isolation parameter,the type name of the network function, one or more parameters comprisinginformation associated with an isolated network slice, and/or the like.The NRF 130 may select a network function, for example, based on thenetwork isolation information parameter. The NRF 130 may perform steps2501-2504 described below regarding FIG. 25, for example, after or inresponse to the SMF 160 sending the discovery request message.

At step 2407, the SMF 160 may send, to the UDM 140, a subscriber datarequest message comprising the network slice isolation parameter. Step2407 may correspond to step 1502 described above regarding FIG. 15. TheSMF 160 may send the subscriber data request message after or inresponse to receiving an N11 message. The subscriber data requestmessage may comprise a second message indicating that subscriber data isrequired for determining a network function. The second message maycomprise the network slice isolation parameter, information associatedwith a subscriber and/or a wireless device, one or more parameterscomprising information associated with an isolated network slice, and/orthe like. Additionally or alternatively, the NRF 130 may perform step2407, for example, after receiving a discovery request message (e.g.,after step 2406).

At step 2408, the SMF 160 may receive an identifier of a UPF (e.g., UPF110) or other network function that satisfies one or more sliceisolation constraints. Step 2408 may correspond to step 1405 describedabove regarding FIG. 14 and/or step 1503 described above regarding FIG.15. The SMF 160 may receive the identifier, for example, from the NRF130 (e.g., after step 2406) and/or from the UDM 140 (e.g., after step2407). The SMF 160 may receive a response message comprising theidentifier of the UPF 110. The response message may be in response tothe discovery request message (e.g., from step 2406) and/or in responseto the subscriber data request message (e.g., from step 2407). Theresponse message may comprise a network function identifier, one or moreIP address(es), and/or the like, that may be associated with a networkfunction (e.g., UPF). The network function may be selected (e.g., by theSMF 160, NRF 130, and/or UDM 140) based on the type name of the networkfunction. The network function may comprise a user plane function, forexample, the UPF 110. The network function identifier may be a fullyqualified domain name (FQDN) of the network function.

At step 2409, the SMF 160 may send, to the discovered network function(e.g., the UPF 110), a session establishment request. Step 2409 maycorrespond to step 1406 described above regarding FIG. 14 and/or step1504 described above regarding FIG. 15. The session establishmentmessage may comprise, for example, an N4 session modification, an N4session establishment, and/or the like. The session establishmentrequest may be based on at least one of the network function identifierand/or IP address(es).

At step 2410, the SMF 160 may receive a session establishment response.Step 2410 may correspond to step 1407 described above regarding FIG. 14and/or step 1505 described above regarding FIG. 15. The SMF 160 mayreceive the session establishment response from the discovered UPF. Thesession establishment response may be in response to the sessionestablishment request (e.g., from step 2409).

At step 2411, the SMF 160 may send a session creation and/ormodification response. Step 2411 may correspond to step 1408 describedabove regarding FIG. 14 and/or step 1506 described above regarding FIG.15. The SMF 160 may send the session creation and/or modificationresponse to the AMF 155. The session creation and/or modificationresponse may be in response to the session creation and/or modificationrequest (e.g., from step 2401). The method may end, for example, afterstep 2411. After step 2411, the SMF 160 may send and/or receive uplinkdata and/or downlink data.

FIG. 25 shows an example method that may be performed by an NRF such asthe NRF 130, to provide an isolated network slice. Additionally oralternatively, the method may be performed by a UDM, such as UDM 140, oranother network function. At step 2501, the NRF 130 may receive aregistration request message from one or more UPFs or other networkfunctions. The NRF 130 may store information relating to the one or moreUPFs or other network functions. At step 2502, the NRF 130 may receive anetwork function discovery request for one or more UPFs, or for othernetwork functions, based on network slice isolation information. Thenetwork slice information may comprise one or more network isolationinformation parameters. Step 2502 may correspond to step 1402 describedabove regarding FIG. 14. The one or more network isolation informationparameters may be a factor used to determine a selection rule based on adegree of isolation. At step 2503, the NRF 130 may select a UPF (orother network function), such as UPF 110, from a list of availablenetwork functions. The NRF 130 may select the UPF 110 based on thenetwork slice isolation information. The NRF 130 may select the UPF 110based on the selection rule. The degree of isolation may be determinedbased on at least one isolation policy of a logical full isolation ofnetwork slices, a physical full isolation of network slices, a partiallogical isolation of network slices, a partial physical isolation ofnetwork slices, a number of network functions that may be allowed to beshared among network slices, a type of network functions that areallowed to be shared among network slices, and/or the like. The networkslice may be the network slice instance. The method may end, forexample, after step 2504.

The degree of isolation may be a level of isolation. The level ofisolation may be determined based on the type of network functions thatmay be shared among a set of network slices. The level of isolation maybe based on distance, for example, in terms of constrained isolationdistance. For example, if elements A and C may not coexist and elementsB and C may coexist, then based on a constrained isolation distance of1, elements A and B may coexist, but based on an constrained isolationof distance 2, elements A and B may not coexist. Isolation may be one ormore of a topological isolation (e.g., logical, or physical), afunctional isolation, a physical resource isolation, and/or atransactional isolation. Topological isolation may be a constraint thatmay prevent a UPF from being controlled by an SMF of Slice A and an SMFof Slice B. Functional isolation may be a constraint indicating thatdifferent types of network functions may coexist if they are not of thesame type. As an example, an AMF from Slice A and a SMF from Slice B maycoexist but the SMF of Slice A may not coexist with the SMF of Slice B.A physical resource isolation may be a constraint that may prevent anetwork function (e.g., virtualized network function) of Slice A frombeing deployed on the same physical resources (e.g., hardware) that maybe used by a network function of Slice B. The transactional isolationmay be a constraint that may prevent concurrent and/or simultaneousaccess by the network function of Slice A and the network function ofSlice B.

FIG. 26 shows an example method that may be performed by a wirelessdevice, such as the wireless device 100, and/or that may be performed bya base station, such as the (R)AN 105, to provide an isolated networkslice. At step 2601, the wireless device and/or the base station maysend a request for service associated with an isolated network slice.The request for service may comprise, for example, a NAS request such asdescribed regarding step 1301 of FIG. 13A and/or an N11 message such asdescribed regarding step 1401 in FIG. 14. At step 2602, the wirelessdevice and/or the base station may receive a response to the request forservice associated with the isolated network slice. The response maycomprise, for example, RRC information such as described regarding step1313 of FIG. 13A and/or an N11 message such as described regarding step1408 in FIG. 14. At step 2603, the wireless device and/or the basestation may send uplink data, and/or receive downlink data, for theservice associated with the isolated network slice. The method may end,for example, after step 2603.

One or more features of the disclosure may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features of the disclosure, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a UE, a base station, and the like) toenable operation of multi-carrier communications described herein. Thedevice, or one or more devices such as in a system, may include one ormore processors, memory, interfaces, and/or the like. Other examples maycomprise communication networks comprising devices such as basestations, wireless devices or user equipment (UE), servers, switches,antennas, and/or the like. A network may comprise any wirelesstechnology, including but not limited to, cellular, wireless, WiFi, 4G,5G, any generation of 3GPP or other cellular standard or recommendation,wireless local area networks, wireless personal area networks, wirelessad hoc networks, wireless metropolitan area networks, wireless wide areanetworks, global area networks, space networks, and any other networkusing wireless communications. Any device (e.g., a wireless device, abase station, or any other device) or combination of devices may be usedto perform any combination of one or more of steps described herein,including, for example, any complementary step or steps of one or moreof the above steps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the disclosure. Accordingly, theforegoing description is by way of example only, and is not limiting.

What is claimed is:
 1. A method comprising: receiving, by a sessionmanagement function (SMF) from an access and mobility managementfunction (AMF), a first message indicating a request to establish apacket data unit (PDU) session and comprising a network slice isolationinformation parameter; sending, to a network repository function (NRF)and based on a determination that a user plane function (UPF) isrequired for the PDU session, a second message comprising: the networkslice isolation information parameter; and a network slice identifier ofthe PDU session; receiving, from the NRF and based on the secondmessage, a third message comprising an identifier of a selected UPF,wherein the selected UPF is associated with the network slice identifierof the PDU session; and sending, to the selected UPF, a fourth messagecomprising a request to establish the PDU session.
 2. The method ofclaim 1, further comprising, receiving from the selected UPF, a fifthmessage comprising a response to the request to establish the PDUsession.
 3. The method of claim 1, wherein the first message furthercomprises: an identifier of the PDU session; an identifier of a wirelessdevice associated with the PDU session; and the network slice identifierof the PDU session.
 4. The method of claim 1, wherein the fourth messagecomprises an N4 PDU session establishment request.
 5. The method ofclaim 1, further comprising determining, based on the network sliceisolation information parameter, a UPF selection rule.
 6. The method ofclaim 5, wherein the UPF selection rule comprises an isolation policycomprising at least one of: a logical full isolation of network slices;a physical full isolation of the network slices; or network functionsthat are allowed to be shared among the network slices.
 7. The method ofclaim 5, wherein the UPF selection rule is based on a network slicecoexistence constraint.
 8. A method comprising: receiving, by a sessionmanagement function (SMF) from an access and mobility managementfunction (AMF), a first message indicating a request to establish apacket data unit (PDU) session and comprising a network slice isolationinformation parameter; sending, to a unified data management (UDM) andbased on a determination that a user plane function (UPF) is requiredfor the PDU session, a second message comprising: the network sliceisolation information parameter; and a network slice identifier of thePDU session; receiving, from the UDM and based on the second message, athird message comprising subscriber data for a wireless deviceassociated with the PDU session; selecting, based on the subscriberdata, a first UPF for the PDU session and associated with the networkslice identifier of the PDU session; and sending, to the first UPF, afourth message comprising a request to establish the PDU session.
 9. Themethod of claim 8, further comprising, receiving from the first UPF, afifth message comprising a response to the request to establish the PDUsession.
 10. The method of claim 8, wherein the first message furthercomprises: an identifier of the PDU session; an identifier of thewireless device associated with the PDU session; and the network sliceidentifier of the PDU session.
 11. The method of claim 8, wherein thefourth message comprises an N4 PDU session establishment request. 12.The method of claim 8, further comprising determining, based on thenetwork slice isolation information parameter, a UPF selection rule. 13.The method of claim 12, wherein the UPF selection rule comprises anisolation policy comprising at least one of: a logical full isolation ofnetwork slices; a physical full isolation of the network slices; ornetwork functions that are allowed to be shared among the networkslices.
 14. The method of claim 12, wherein the UPF selection rule isbased on a network slice coexistence constraint.
 15. A methodcomprising: receiving, by a network repository function (NRF) from asession management function (SMF), a first message indicating that auser plane function (UPF) is required for a packet data unit (PDU)session and comprising: a network slice isolation information parameter;and a network slice identifier of the PDU session; selecting, based onthe network slice isolation information parameter and the network sliceidentifier of the PDU session, a first UPF; and sending, to the sessionmanagement function, a second message comprising an identifier of thefirst UPF.
 16. The method of claim 15, further comprising receiving,from a unified data management (UDM), the network slice isolationinformation parameter.
 17. The method of claim 15, further comprising:receiving, from the first UPF, a registration request messagecomprising: a single network slice selection assistance information(S-NSSAI) associated with the first UPF; and an identifier of the firstUPF.
 18. The method of claim 15, further comprising: receiving, from thefirst UPF: a domain name of the first UPF; a data network name; or anaddress of the first UPF.
 19. The method of claim 15, furthercomprising: sending, to a unified data management (UDM), a third messagecomprising: the network slice isolation information parameter; and anetwork slice identifier of the PDU session; and receiving, from the UDMand based on the third message, a fourth message comprising subscriberdata for the wireless device.
 20. The method of claim 19, wherein theselecting the first UPF comprises: determining, based on the subscriberdata for the wireless device, the first UPF for the PDU session.